December 10, 2009 at 2:16 pm
Hello,
I have a SQL Server 2005 that had client components not install successfully during a SP3 (KB955706) upgrade. Server is a Windows Server 2003. Can you help?
Here is what I have done:
Extracted the sqlrun_tools.msp from the SP3 package
Extracted the sqlrun_Tools.msi from SP3 package
Copied both files to the c:\windows\installer folder
Renamed the sqlrun_tools.msp to 3056adde.msp (got the name from the log file)
Renamed the sqlrun_tools.msi to 8837b23.msi (got the name from the log file)
When I run the MSP file, I get this error:
Error 2902. The installer has encountered an unexpected error. The error code is 2902. Operation ixfAssemblyCopy called out of sequence.
These log files are from when I ran the SP3 upgrade.
The summary.txt
----------------------------------------------------------------------------------
Product : Client Components
Product Version (Previous): 3054
Product Version (Final) :
Status : Failure
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB955706_sqlrun_tools.msp.log
Error Number : 1635
Error Description : Unable to install Windows Installer MSP file
From the SQLTools9_Hotfix_KB955706_sqlrun_tools.msp.log:
******* CommandLine: **********
MSI (s) (BC:14) [03:03:50:867]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (BC:14) [03:03:51:038]: End dialog not enabled
MSI (s) (BC:14) [03:03:51:038]: Original package ==> C:\WINDOWS\Installer\8837b23.msi
MSI (s) (BC:14) [03:03:51:038]: Package we're running from ==> C:\WINDOWS\Installer\8837b23.msi
MSI (s) (BC:14) [03:03:51:492]: APPCOMPAT: looking for appcompat database entry with ProductCode '{4D2DFB70-AECB-47BF-A895-3B3AA544934F}'.
MSI (s) (BC:14) [03:03:51:492]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (BC:14) [03:03:51:492]: MSCOREE not loaded loading copy from system32
MSI (s) (BC:14) [03:03:51:492]: Opening existing patch 'C:\WINDOWS\Installer\3056adde.msp'.
MSI (s) (BC:14) [03:03:51:492]: Note: 1: 2203 2: C:\WINDOWS\Installer\3056adde.msp 3: -2147287038
MSI (s) (BC:14) [03:03:51:492]: Opening existing patch 'C:\WINDOWS\Installer\3056adde.msp'.
MSI (s) (BC:14) [03:03:51:492]: Note: 1: 2203 2: C:\WINDOWS\Installer\3056adde.msp 3: -2147287038
MSI (s) (BC:14) [03:03:51:492]: Couldn't find local patch 'C:\WINDOWS\Installer\3056adde.msp'. Looking for it at its source.
MSI (s) (BC:14) [03:03:51:492]: Resolving Patch source.
MSI (s) (BC:14) [03:03:51:523]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (BC:14) [03:03:51:523]: User policy value 'DisableMedia' is 0
MSI (s) (BC:14) [03:03:51:523]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (BC:14) [03:03:51:523]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (BC:14) [03:03:51:523]: SOURCEMGMT: Looking for sourcelist for product {88591C3A-E392-4B2C-98B7-F123862FD540}
MSI (s) (BC:14) [03:03:51:523]: SOURCEMGMT: Adding {88591C3A-E392-4B2C-98B7-F123862FD540}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (BC:14) [03:03:51:523]: SOURCEMGMT: Now checking product {88591C3A-E392-4B2C-98B7-F123862FD540}
MSI (s) (BC:14) [03:03:51:523]: SOURCEMGMT: Media is enabled for product.
MSI (s) (BC:14) [03:03:51:523]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (BC:14) [03:03:51:523]: SOURCEMGMT: Trying source y:\f882c46cda7039ead8\HotFixTools\Files\.
MSI (s) (BC:14) [03:03:51:523]: Note: 1: 2203 2: y:\f882c46cda7039ead8\HotFixTools\Files\sqlrun_tools.msp 3: -2147287037
MSI (s) (BC:14) [03:03:51:523]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (BC:14) [03:03:51:523]: Note: 1: 1706 2: -2147483647 3: sqlrun_tools.msp
MSI (s) (BC:14) [03:03:51:523]: SOURCEMGMT: Processing net source list.
MSI (s) (BC:14) [03:03:51:523]: Note: 1: 1706 2: -2147483647 3: sqlrun_tools.msp
MSI (s) (BC:14) [03:03:51:523]: SOURCEMGMT: Processing media source list.
MSI (s) (BC:14) [03:03:52:570]: SOURCEMGMT: Resolved source to: 'sqlrun_tools.msp'
MSI (s) (BC:14) [03:03:52:773]: Note: 1: 1314 2: sqlrun_tools.msp
MSI (s) (BC:14) [03:03:52:773]: Unable to create a temp copy of patch 'sqlrun_tools.msp'.
MSI (s) (BC:14) [03:03:52:773]: Note: 1: 1708
MSI (s) (BC:14) [03:03:52:773]: Note: 1: 2729
MSI (s) (BC:14) [03:03:52:788]: Note: 1: 2729
MSI (s) (BC:14) [03:03:52:788]: Product: Microsoft SQL Server 2005 Tools -- Installation failed.
MSI (s) (BC:14) [03:03:52:820]: MainEngineThread is returning 1635
This patch package could not be opened. Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.
C:\WINDOWS\Installer\8837b23.msi
MSI (c) (F0:D4) [03:03:52:820]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (F0:D4) [03:03:52:820]: MainEngineThread is returning 1635
=== Verbose logging stopped: 12/5/2009 3:03:52 ===
December 10, 2009 at 4:01 pm
Install from the original media, then run SP3 again to upgrade just those components.
Joie Andrew
"Since 1982"
December 10, 2009 at 4:42 pm
Could I use the Windows Installer Cleanup Utility to remove old SQL install files? Do I select the MS SQL Server Setup Support Files in the utility to do this?
December 11, 2009 at 12:50 am
I think I was unclear before. I apologize. The tools install you were trying to run is an msp file. It cannot be applied by itself, it needs to reference the original msi install before patching anything to the newest version. Since you never installed the tools from the original media, there is nothing for it to find to upgrade, so it fails. If you insert the original SQL Server 2005 RTM media and install only those components you need, you should then be able to pop in the SP3 disk, run the update, and it will identify those newly installed components that are not at SP3.
Joie Andrew
"Since 1982"
December 11, 2009 at 10:01 am
Thank you for the tips. I was successfully able to run he MSP file, so I think it found the MSI file and install the client components.
To clean up old setup files from SQL Server or the SP3, could I use the Windows Installer Cleanup Utility to remove these install files? Do I select the MS SQL Server Setup Support Files in the utility to do this?
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply