Problem with sql2005-kb918222-x86-enu.exe (cumulative hotfix, build 2153)

Hello,

I do experiment a problem when trying to install the mentionned patch on my Windows XP SP2 machine (fully patched).

Interestingly, the patch works fine for the named instance, which is a "clean" install of SQL Server 2005 SP1, while it fails on the default instance, which is a SQL 2005 SP1 upgraded in place from SQL Server 2000 SP4. Both instances are Developer editions...

The error is along the following lines:

[snip]

08/10/2006 09:22:06.728 Unable to install MSP file: \\DHDHY0J\c$\1c7c01591e524f9a092159a233\hotfixsql\Files\sqlrun_sql.msp
08/10/2006 09:22:06.818 The following exception occurred: Unable to install Windows Installer MSP file Date: 08/10/2006 09:22:06.818 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 856
08/10/2006 09:22:06.948
08/10/2006 09:22:06.998 Product Status Summary:
08/10/2006 09:22:07.048 Product: SQL Server Database Services 2005
08/10/2006 09:22:07.088 MSSQLSERVER - Failure
08/10/2006 09:22:07.138 Details: Unable to install Windows Installer MSP file
08/10/2006 09:22:07.228 SQL2K5 - Not Selected
08/10/2006 09:22:07.338
08/10/2006 09:22:42.409 Hotfix package closed

Any thoughts somebody?

Thanks in advance,

Emmanuel

Emmanuel, can you search your %windir%\hotfix\ folder for the text string "value 3" and include the 10 or so lines on each side. This should be in the sqlrun_sql.msp file and will help us troubleshoot.

Thanks,
Samuel Lester (MSFT)

|||

Hello,

thank you for your input. I could not locate the string "value 3" in the file you mentionned. So I put up my sleeves and decided to dig in this 12Mb+ file... Finally, I found a few interesting entries, and could narrow down my problem to security config: on my machine, the service was running as a normal, non-privileged user (i.e. not member of local admins), and to avoid anti-virus slow-down, I had special security placed on key files allowing access to only this very user. (No, I cannot exclude the files from within the anti-virus because of corporate policies).

I changed back, and the setup ran normally. Sorry for the trouble.

Oh Yes, the named instance is not used usually. Just there for having an installation try, and to be able to compare "clean" vs upgrade install. Therefore no special config on this instance ...

With kind regards,

Emmanuel

sql