Re: WMI Config Error Installing SQL2K5 Standard Edition

"Eric" wrote:

> 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
> (0W80004002)."
>
> 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.
>
>