Have you encountered a problem due to deletion of the contents of C:\Windows\Installer folder? Several times the administrators delete the contents of this folder to make the space free without knowing the consequences. All the previous installation files get stored to this folder specifically the update\patches files which comes in to use when we upgrade the patch or any specific application. So please do use the “Installer cleanup utility” provided by Microsoft for cleaning C:\Windows\Installer folder.

In this article I will discuss as how to resolve the problem if you are unable to install the SQL Server 2005 SP3 due to previous installer files deleted.  We have recently faced this when we were trying to update our Database Service pack. One of our administrators deleted the contents of C:\Windows\Installer folder to mitigate the space crunch faced on the system volume(C: Drive) and resulting which we were unable to install the SQL Server 2005 SP3.

If you are facing the same issue then the solution goes as follows-

1.)    Start the SQL Server 2005 SP3 installation. When it fails refer to the log file.

2.)    You can refer the installation log stored at “C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB955706_sqlrun_tools.msp.log” the path may differ according to your installation.

3.)    When you will refer this log file you will find it is unable to find one .msp file which ideally should be in .\windows\installer folder. This file name is different for each n every server. Now the work around will be as below-

“Download the SQL Server 2005 SP2 if you have it already then it’s cool. Extract the *.exe by using /extract or /x switch to a folder. Now search for “sqlrun_sql.msp” file. Rename this file by copying it somewhere else to the same name which the log file is showing missing in c:\windows\installer folder and paste the file to C:\windows\installer folder.

4.)    Now run the SP3 setup again. It should be completed this time. But if still fails, refer the log file again. Now what you will found that that it has found the previously missed .msp file but got struck at the second .msp file (In my case it was like this). Now the workaround is-

“Go Ahead and download SQL Server 2005 SP1 and extract it the same way as we did about SP2 now again search for “sqlrun_sql.msp” file and paste it to the c:\windows\installer and rename it to the the name which log file is showing missing.”

Now run the SP3 setup again and this time you should be successful.

The Sample Installation Log File

*************************************************************

MSI (s) (44:80) [14:29:07:518]: Note: 1: 2262 2: UIText 3: -2147287038

MSI (s) (44:80) [14:29:07:518]: Note: 1: 2262 2: Media 3: -2147287038

MSI (s) (44:80) [14:29:07:518]: Note: 1: 2262 2: Shortcut 3: -2147287038

MSI (s) (44:80) [14:29:07:518]: Note: 1: 2262 2: SxsMsmGenComponents 3: -2147287038

MSI (s) (44:80) [14:29:07:518]: Note: 1: 2262 2: MsiSFCBypass 3: -2147287038

MSI (s) (44:80) [14:29:07:518]: Note: 1: 2262 2: RemoveFile 3: -2147287038

MSI (s) (44:80) [14:29:07:518]: Note: 1: 2262 2: RemoveRegistry 3: -2147287038

MSI (s) (44:80) [14:29:07:518]: Note: 1: 2262 2: Environment 3: -2147287038

MSI (s) (44:80) [14:29:07:518]: Note: 1: 2262 2: _sqlUpgradeFile 3: -2147287038

MSI (s) (44:80) [14:29:07:518]: Note: 1: 2262 2: _sqlUpgradeRegistry 3: -2147287038

MSI (s) (44:80) [14:29:07:518]: Note: 1: 2262 2: _sqlUpgradeFolders 3: -2147287038

MSI (s) (44:80) [14:29:07:518]: Note: 1: 2262 2: _MsiPatchTransformView 3: -2147287038

MSI (s) (44:80) [14:29:07:518]: Opening existing patch ‘C:\WINDOWS\Installer\2691b4.msp’.———-“In first failure this msp file was causing failure.”

MSI (s) (44:80) [14:29:07:518]: Opening existing patch ‘C:\WINDOWS\Installer\389d4c59.msp’.———“In second failure this msp file was causing failure.”

MSI (s) (44:80) [14:29:07:518]: File will have security applied from OpCode.

MSI (s) (44:80) [14:29:14:394]: Original patch ==> d:\604b2713b936ee0404\HotFixSQL\Files\sqlrun_sql.msp

MSI (s) (44:80) [14:29:14:394]: Patch we’re running from ==> C:\WINDOWS\Installer\8ecaac.msp

MSI (s) (44:80) [14:29:14:394]: Opening existing patch ‘C:\WINDOWS\Installer\4208e404.msp’.