The SQL Server System Configuration Checker cannot be executed due to WMI configuration on the machine <machineName> Error: 21475000034 (0x80004002)
SPECIAL NOTE: Please read this entire post before attempting any of the options that I describe - things are not all that they seem. The final solution did require re-loading the OS. It came down to my opening the UAC and then installing AIM. No matter what I did after that - WMI would hose up if I was trying to install anything like SQL Server, BizTalk Server - you name it. Sorry for the lengthy post - but I suspected someone else would learn from this.
If you receive the above error - when trying to install SQL Server 2005 Developer, Standard, or Enterprise, on a Vista workstation...
You have probably read this thread - http://sqljunkies.com/Forums/ShowPost.aspx?PostID=85
Further - MSDN here - http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=131970&SiteID=1
HOWEVER
Is the Registry setting set to zero for the UAC on Vista? I thought this may be the issue as I leave it turned off - and I found many posts online regarding how WMI can be affected when you turn this off - some setup applications will fail without any real error message or event entry regarding why it failed. So I turned UAC back on:
I use REGEDIT and edit HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System - and set EnableLUA to '0'
ADDITIONAL SETTINGS
- I also found the following information provided by Product Support Services for another person running into a similar issue:
- 1. Add network service account to administrators group.
- 2. Add authenticated users to following registry keys: * HKCR\CLSID\{73E709EA-5D93-4B2E-BBB0-99B7938DA9E4} * HKCR\CLSID\{7C857801-7381-11CF-884D-00AA004B2E24} * HKLM\Software\Microsoft\WBEM\CIMOM
This person gave the local\Authenticated Users group Full Control on these registry keys...
The first registry key is the Launch permission on the WMI Provider Subsystem:
The second registry key is the access to wbemsvc.dll:
The third key deals with much more - and I suspect is the crux of the solution:
Nonetheless, I followed the instructions:
NOTE regarding Authenticated Users: If your workstation/notebook is connected to a domain - you will need domain Administrator permissions to change the add user to the Local Machine when you are adding the Authenticated Users to these registry keys - you cannot add a domain scoped Authenticated Users to the keys - only for the local machine.
FINDINGS
The above did not work for me on this Vista Ultimate host. I found additional PSS support tickets with the following:
- Also you can try running the following from a command prompt :
- Mofcomp.exe %windir%\system32\wbem\cimwin32.mof
- Regsvr32 %windir%\system32\wbem\wbemupgd.dll
- Regsvr32 %windir%\system32\wbemwbemsvc.dll
The second regsvr32 entry for wbemupgd.dll returned an error for me that the DLL did not exist.
Alas - my problem continues to persist.
The following is a snippet from my installed programs - of special notice is that I have Visual Studio 2005 Tools for Applications SDK February 2007 installed.
On the following link - http://download.microsoft.com/download/2/b/5/2b5e5d37-9b17-423d-bc8f-b11ecd4195b4/ReadmeSQL2005SP2.htm - I found - down at 5.5.1 Scripting Incompatible with Microsoft Windows Vista the blurb about VSTA installing something that appears to be the culprit.
Uninstalling VSTA - did not solve the problem.
Extensive review of online MSDN Forums, and even some PSS tickets on Connect.MSFT - etc - for SQL Server - convey that the problem is much more nefarious than anything I've turned up thus far - and that WMI is the root of the issue - and my guess is - something has become corrupt w/WMI.
I've run the WMI Diags 2.0 utility from MSFT - and it showed 16 succinct errors where MOF (Managed Object Format) files were not being restored / instantiated successfully. Alas - my woes are just beginning...
WMI and the Art of Zen
I found the following instructions at - http://searchwincomputing.techtarget.com/tip/0,289483,sid68_gci1160143,00.html
- 1. At the command line, type net stop winmgmt. You may get a warning that other services need to be stopped as well; type Y and continue.
- 2. Open Explorer and go to the folder called %SystemRoot%\System32\WBEM\Repository.
- 3. Delete that folder and everything in it.
- 4. Reboot the system normally.
- 5. On the next login, open a command prompt and type the following commands in this order:
winmgmt /clearadap
winmgmt /kill
winmgmt /unregserver
winmgmt /regserver
winmgmt /resyncperf - This procedure will force the WINMGMT service to re-register itself as well, although, if WMI is damaged, re-registering can be a problem. If this approach does not work, an in-place upgrade (i.e., a reinstall) might be required.
FINAL ANALYSES
I was not able, under any circumstances - to get any of the foregoing to work for me. I wound up reloading the notebook from scratch. Sorry I could not provide you an easy work-around.