D. McCallie


This is (some of) the output from the Core(Local)log:

If possible, determine action
Machine = DJONES-XP, Article = WMIServiceWin32OSWorking, Result = 2147500034 (0x80004002)
Machine = DJONES-XP, Article = WMIServiceWin32CompSystemWorking, Result = 2147500034 (0x80004002)
Machine = DJONES-XP, Article = WMIServiceWin32ProcessorWorking, Result = 2147500034 (0x80004002)
Machine = DJONES-XP, Article = WMIServiceReadRegWorking, Result = 0 (0x0)
Machine = DJONES-XP, Article = WMIServiceWin32DirectoryWorking, Result = 70347 (0x112cb)
Machine = DJONES-XP, Article = WMIServiceCIMDataWorking, Result = 70347 (0x112cb)
Machine = DJONES-XP, Article = XMLDomDocument, Result = 0 (0x0)
*******************************************
Setup Consistency Check Report for Machine: DJONES-XP
*******************************************
Article: WMI Service Requirement, Result: Error
Description: Windows Management Instrumentation (WMI) is not functioning properly. Further checks cannot be performed. Action: Please make sure Windows Management Instrumentation (WMI) is functioning properly.
The SQL Server System Configuration Checker cannot be executed due to WMI configuration on the machine DJONES-XP Error:2147500034 (0x80004002).
The checkResult returned is 2147500034
The checkResult for local machine returned by CheckSCCResult is 70036
Setup is unable to proceed because one of scc articles failed. Please address those errors before continuing the setup.

Thanks DeWayne




Re: WMI Config Error Installing SQL2k5 Standard Edition

Jin Feng - MSFT


Hi,

the error code 0x80004002 in the log is E_NOINTERFACE. Not sure why, but here is what you can do:

1. start->run->cmd.exe

2. net stop winmgmt

3. net start winmgmt

4. start->run->wbemtest.exe

5 click "connect", type in "root\cimv2", click "connect" button

6.click "Enum Instances...", type in "win32_processor", click OK

If all steps above succeeds, please try to run setup again.

If not, please share which step fails and with what error. These steps involve no SQL setup, so we can isolate if this WMI issue you're seeing is related to SQL setup or OS only.

Last thing, if still not successful, can you run these two commands

1. in cmd prompt window: run

winmgmt /verifyrepository

2. if it returns something about inconsistency, run this

winmgmt /salvagerepository

then try setup again.

Hope it helps, please let us know the results. Thanks!







Re: WMI Config Error Installing SQL2k5 Standard Edition

Jin Feng - MSFT

D. McCallie,

Does the winmgmt /salvagerepository work for you

Jin







Re: WMI Config Error Installing SQL2k5 Standard Edition

PierreGermany

Hello Jin Feng,

I've the same problem as D. McCallie. I tried to do like you explained, but at the following step occurs an error:

6.click "Enum Instances...", type in "win32_processor", click OK

The following error occured:

Nummer: 0x80004002
Einrichtung: <Null>
Beschreibung: Schnittstelle nicht unterstutzt (meens Interface not supported)

Please help ;-)





Re: WMI Config Error Installing SQL2k5 Standard Edition

EricJudge06

Hi I have the same error trying to install SQL Server 2005 Standard edition. I went through the steps mentioned above and got an error on step 6 trying to enter win32_processor. I got the following Error dialog box:

Number: 0x80004002
Facility: <Null>
Description: No such interface supported

And below that are buttons for Dismiss and More Information.

Any help is greatly appreciated. I've been searching online for about 10 hours now and have tried a bunch of different fixes and WMI troubleshooting suggestions but nothing is working for me.

Thanks...





Re: WMI Config Error Installing SQL2k5 Standard Edition

Murtaza90

Hi! I hv tried to instal sql server 2005 express edition. But after repeated attempts I get the same error :

"The SQL Server System Configuration Checker cannot be executed due to WMI configuration on the machine SYS503-03 Error:2147749891 (0x80041003)"

Iam stuck at this.. plz . if any could help about it!!!!

Thanx,






Re: WMI Config Error Installing SQL2k5 Standard Edition

EricJudge06

After much searching I found a fix posted online that got me past this error. Someone posted on his blog that he was getting the same error on another installation and he had called Microsoft Support about it. Here is the link to his blog and the fix he said Microsoft gave him:

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

http://michalferber.com/index.php/page/6/

I started installing Visual Studio 2005 the other day and kept getting this error.

¡°The SQL Server System Configuration Checker cannot be executed due to WMI configuration on the machine FERBER Error:2147500034 (0¡Á80004002).¡±

I searched high and low and found nothing of any value. So I called in the experts (Microsoft Support).

It turns out that something was screwy with WMI on my machine. We did the following after a few hours trying different things and then the install was successful.

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

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

I would also add¡­

To do step 1, you go to Control Panel, User Accounts, Advanced tab, click Advanced button, and open Groups folder.

To do step 2, right click on those registry keys, click Permissions, and add Authenticated Users. I gave them Full Control permissions, but I¡¯m not sure if that was necessary or not.

Lastly, I don't think this is a pure fix to the way the WMI configuration is supposed to be. When I run the WMI diagnostics again, most of the errors are gone, but I still get the errors related to namespace security and default trustees being removed. And at the bottom it still says "ERROR: WMIDiag detected issues that could prevent WMI to work properly." My guess is these permissions changes to the registry overrided whatever missing permissions the diagnostics tool is looking for. Nevertheless the diagnostics tool is still looking for the permissions in the original places and not finding them. But since this solution came from Microsoft and it seems to work, I'm satisfied with it.