Thursday, February 16, 2012

Can''t install the client components, error raised

Hi,

when I try to install the client components I receive this error:

Upgrade failed due to the following error. The error code is:

-2147467259. Message: Unspecified error

I think the problem is during the upgrade of the report server components.

my computer has the SQL 2005 client components installed but I have just uninstall these components.

I'll try on a second computer , the first one is Vista, the second is XP SP2.

I have opened a connect issue around this error including the complete log.

thanks for your guides.

For info:

the same steps on an XP SP2 station works fine.

(removing SQL 2005 client components and then installing SQL 2008 client components)

|||

In the katmai site has a document speaking that before you install katmai,remove the workstation components of Sql Server 2005...

4.3.3 Installing SQL Server "Katmai" Removes Support for DTS in SQL Server 2005 Integration Services Packages

For this CTP release, you must uninstall SQL Server 2005 Workstation Components before installing the SQL Server "Katmai" Workstation Components. Uninstalling the SQL Server 2005 Workstation Components removes three Integration Services components: the SQL Server 2005 version of the Execute DTS 2000 Package task and two supporting assemblies. These three Integration Services components support backward compatibility between SQL Server 2005 and SQL Server 2000 Data Transformation Services (DTS). Without these three components, SQL Server 2005 packages and tools that require DTS support will not run.

However, SQL Server "Katmai" Integration Services includes a version of the Execute DTS 2000 task and the two supporting assemblies. Therefore, you can upgrade SQL Server 2005 packages that require DTS support to the SQL Server "Katmai" format by opening them in the SQL Server "Katmai" version of Business Intelligence Development Studio, and then running those packages as SQL Server "Katmai" packages.

|||

I have removed everything from SQL 2005 and the error still here only on my Vista station.

I try to install each client component 1 by 1 and the error is raised when I try to install the BIDS (dev studio) component.

The server components can be installed without any issue.

|||Willgart,

On the succesful xp installation (where you un-installed the S2K5 client bits first), did you have CLR 2.0 installed on that box?

The reason I'm asking is that from my tests, it fails if you have CLR 2.0 installed when you do the Katmai installation, and Vista does have CLR 2.0 installed by default (iirc), but not xp.

Niels
|||I got the same "Upgrade failed due to the following error. The error code is:

-2147467259. Message:Unspecified error" message. I had uninstalled the SQL 2005 programs. Win XP SP2, VS 2005, Office 2007. I ran it from servers\splash.hta. This was the last Product, Workstation Components, Books Online and Development Tools. Any ideas?

The last page of the log is:

Property(S): SqlDefaultWebSite = /W3SVC/1
Property(S): SqlASPNETInstalled = 1
Property(S): SqlCOMPlusInstalled = 1
Property(S): RSPREREQUISITECHECKED = 1
Property(S): RSSqlPoolLimit = 100
Property(S): RSGUIDVALUE = {4a8abfef-1c99-4619-be39-8545354bd776}
Property(S): RemoveFeatureList = Client_Components,Connectivity,SQL_Tools,SQL_WarehouseDevWorkbench,SDK,SQLXML,Tools_Legacy,TOOLS_BC_DEP,SQL_Documentation,SQL_Samples,SQL_BooksOnline,SQL_DatabaseSamples
Property(S): SqlOriginalMachineName = 06LP201
Property(S): Namechecksumcommon_32 = Developer Edition
Property(S): SqlSubDir = \MSSQL
Property(S): EditionTypechecksumcommon_32 = Developer Edition
Property(S): Namechecksumtools = Developer Edition
Property(S): EditionTypechecksumtools = Developer Edition
Property(S): ValidMOFInstanceName = 1
Property(S): ROOTDRIVE = D:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): RSVirtualDirectoryServer = ReportServer
Property(S): RSVirtualDirectoryManager = Reports
Property(S): SOURCEDIR = C:\Temp\SQL Server Katmai Developer Edition X86, English\tools\Setup\
Property(S): SourcedirProduct = {D6251ACA-3FD4-49D1-8FCF-182B980B19E3}
Property(S): HxDs_Tmp_3643236F_FC70_11D3_A536_0090278A1BB8 = C:\DOCUME~1\ccook\LOCALS~1\Temp\HxC0D.tmp
Property(S): HxDs_Tmp_Hash_3643236F_FC70_11D3_A536_0090278A1BB8 = B40B0DC6C3C19C68E0101E0E2A647F0C3A18F6
Property(S): InstallNgenTicks = 2310000
Property(S): ProductToBeRegistered = 1
MSI (s) (08Big Smile8) [10:44:52:780]: Note: 1: 1708
MSI (s) (08Big Smile8) [10:44:52:780]: Product: Microsoft SQL Server "Katmai" Tools -- Installation failed.

MSI (s) (08Big Smile8) [10:44:52:820]: Cleaning up uninstalled install packages, if any exist
MSI (s) (08Big Smile8) [10:44:52:820]: MainEngineThread is returning 1603
MSI (s) (08:60) [10:44:52:931]: Destroying RemoteAPI object.
MSI (s) (08:2C) [10:44:52:931]: Custom Action Manager thread ending.
=== Logging stopped: 6/8/2007 10:44:52 ===
MSI (c) (8C:70) [10:44:52:971]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (8C:70) [10:44:52:971]: MainEngineThread is returning 1603
=== Verbose logging stopped: 6/8/2007 10:44:52 ===

|||

Hi,

As Willgart wrote database engine is installed without any problem.

But the client components seems to create problem during the installation.

I worked some on installing the client components of Katmai on Windows Server 2008 Beta3.

You can read my experience on installing the client components of Katmai at my blog http://www.kodyaz.com/blogs/software_development_blog/archive/2007/06/10/567.aspx

As a short brief I uninstalled the workstation tools of SQL2005, restart and then run the msi package from \tools\setup\sqlrun_tools.msi

This method successfully installed the client tools of Katmai side by side a SQL2005 instance.

Eralper

http://www.kodyaz.com

|||

I have allready try this method to install the client components but I suffer the same error.

|||

This problem usually occurs if you have Microsoft Visual Studio 8 installed in a non-default location.

Please confirm if you have VS8 installed in a non-default location. If so, setup cannot find the following file and causes this problem:

C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\devenv.exe.config

If you put the missing file there and retry, setup should succeed.

|||

yes!

copying the file is the solution, I can successfully install the client components on my Vista station.

thanks.

|||

Well....

the installation was done, but none of the visual studio components works fine!

everytim I try to open a solution or create a new one I receive a lot of error (component not found and VS ask me to disable the non working component)

so it's certainly related to my VS setup which is not in the c: folder.

so I'll wait for the next release.

|||

Hi,

I had the same problem with installing the workstation components, but I tried to install the system on clean new VirualPC Windows Server 2003 SP1 nothing else installed....

BUT!: I installed .NET framework 2.0 and the .NET Framework 2.0 SDK before SQL-Server 2008 !!!!

After removing SDK, installation finished successfully !!!

Hope that helps!

|||I first assumed that it was problems with <SQL Server 2000 DTS Designer Components> but I don't think that was the main reason for this error message.
I can confirm that there are some problems installing SQL Server 10.0.1019 components when Microsoft .Net Framework 2.0 allready is installed (with patch).
I tried to install SQL server several times with same error messange until I uninstalled exsisting .Net Framework installation. It seems that components want to use the .Net Framework 2.0 that is bundled with SQL server.|||

Hi people! This is my first post here, with the same problem that the rest of you, except that my platform is Windows Server 2008 B3. I can install the DB engine but can't install client tools... any ideas? Tip: i've already installed Sharepoint Services v3.0 (with its own database engine... maybe the problem come from there....)

Agustín

No comments:

Post a Comment