Unable to install SQL 2008 due to the remnants of a previous installation
Sometime remnants of a previous installation/ a failed install can prevent us from reinstalling SQL server
I have documented the consequence of one such instance which rendered us to be unable to install SQL 2008 from the server
· When we launched the setup we got the following error :
SQL Server Setup failure. 1
SQL Server Setup has encountered the following error:
MsiGetProductlnfo failed to retrieve Productversion for package with Product Code = ‘{DF167CE3-60E7-44EA-99EC-2507C 5 1F37AE}’. Error code: 1605..
We got the obfuscated product code :
---------------------------
Obfuscated product code Result
---------------------------
3EC7S1FD7E06AE4499CE52705CF173EA
---------------------------
OK
---------------------------
· Went into the registry (start-->run-->regedit) and took a full registry backup
· We then went to the following key HKEY_CLASSES_ROOT\Installer\UpgradeCodes
· We then used the obfuscated product code : 3EC761FD-7E06-AE44-99CE-52705CF173EA
· We searched for it within the registry key HKCR\Installer\UpgradeCodes for matches.
· We got one match and deleted its parent.
· We ran the installation which failed yet again with this error :
TITLE: SQL Server Setup failure.
------------------------------
SQL Server Setup has encountered the following error:
MsiGetProductInfo failed to retrieve ProductVersion for package with Product Code = '{DF167CE3-60E7-44EA-99EC-2507C51F37AE}'. Error code: 1605..
------------------------------
BUTTONS:
OK
------------------------------
· We navigated to this key :HKEY_CLASSES_ROOT\Installer\Features\3EC761FD7E06AE4499CE52705CF173EA and saw that we were having issues (access denied ) issues with it
· We obfuscated the GUID again : DF167CE360E744EA99EC2507C51F37AE , we searched for it and found a key
· We added everyone to the root and added the full control to administrators, System and even replace permission entries to all sub-keys. Same error.
· Since we not have any special changes/permissions set, decided to reset the registry permissions(needs to be used with caution , contingent on the fact that we do not have customized permissions set on the registry)
· We used the KB : https://support.microsoft.com/kb/313222 to reset the permissions so that the setup program will have access to it
· We got this error again from the setup:
MSI error description: Could not open key: UNKNOWN\Components\00C004FEE241478418DBB8505B78CBC5\D56941F2B76595E4DABEA0C21C3EDAFD. Verify that you have sufficient access to that key, or contact your support personnel.
TITLE: Microsoft SQL Server 2008 Setup
------------------------------
The following error has occurred:
Could not open key: UNKNOWN\Components\9419DB21C522CF24897B0DF659D5B883\5B3A043535835474EB2DDDF95F733113. Verify that you have sufficient access to that key, or contact your support personnel.
------------------------------
MSI error description: Could not open key: UNKNOWN\Components\00C004FEE241478418DBB8505B78CBC5\D56941F2B76595E4DABEA0C21C3EDAFD. Verify that you have sufficient access to that key, or contact your support personnel.
· Every time setup for giving us errors for different GUID's
· The registry permissions were altered to prevent us from running the setup
· We used this KB : https://support.microsoft.com/kb/237607 to use the Regini.exe tool to modify registry permissions from within a script.
· While trying to reset the permissions on 2 registry entries we are getting the following message.
REGINI: CreateKey (\registry\machine\SOFTWARE\Microsoft\Windows\CurrentVersion\I
nstaller\UserData\S-1-5-18\Components\9419DB21C522CF24897B0DF659D5B883\5B3A04353
5835474EB2DDDF95F733113) relative to handle (000000000) failed - 5
REGINI: Failed to load from file 'c:\Users\msm\Desktop\test.txt' (5)
· We then took the permissions on the following hive : \SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components and then replace the security permissions on the sub keys
· This time the setup of SQL server went through successfully
Regards,
Amrutha Varshini J
SE, Microsoft SQL Server
Comments
- Anonymous
December 02, 2012
The comment has been removed