Microsoft Developer Network > Forums Home > Visual Studio Express Editions Forums > Installing and Registering Visual Studio Express Editions > Receiving WMI configuration error. SQL Server System Configuration cannot be executed due to that
Ask a questionAsk a question
 

AnswerReceiving WMI configuration error. SQL Server System Configuration cannot be executed due to that

  • Saturday, January 07, 2006 4:02 AMI Mrus Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hello PPl,

    I am getting this error again and again.

    The SQL Server System Configuration Checker cannot be executed due to WMI configuration on the machine mymachine Error:2147749896 (0x80041008).

     

    I uninstall all version of Visual Studio 2005 just kept Microsoft .NET Framework 2.0.  Still I am getting this error when I am running SQLEXPR.exe to install the SQL Server 2005 Express.

     

    PLEASE HELP!

     

    Thank you. 

Answers

  • Monday, January 30, 2006 4:55 PMbwalkertn Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    I found this batch file and ran it and it fixed my WMI problems on SQL Server 2003.  Copy this into notepad as save as fixwmi.cmd and then from a command line run c:\fixwmi.cmd.

    It takes several minutes to complete and at points it appears that it is not running but it is.  After it is complete, you see the :END statement start the SQL server installation again and you should be fixed.

     

    FIXWMI.CMD
    ------------------------

    @echo on
    cd /d c:\temp
    if not exist %windir%\system32\wbem goto TryInstall
    cd /d %windir%\system32\wbem
    net stop winmgmt
    winmgmt /kill
    if exist Rep_bak rd Rep_bak /s /q
    rename Repository Rep_bak
    for %%i in (*.dll) do RegSvr32 -s %%i
    for %%i in (*.exe) do call :FixSrv %%i
    for %%i in (*.mof,*.mfl) do Mofcomp %%i
    net start winmgmt
    goto End

    :FixSrv
    if /I (%1) == (wbemcntl.exe) goto SkipSrv
    if /I (%1) == (wbemtest.exe) goto SkipSrv
    if /I (%1) == (mofcomp.exe) goto SkipSrv
    %1 /RegServer

    :SkipSrv
    goto End

    :TryInstall
    if not exist wmicore.exe goto End
    wmicore /s
    net start winmgmt
    :End

All Replies

  • Monday, January 30, 2006 4:55 PMbwalkertn Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    I found this batch file and ran it and it fixed my WMI problems on SQL Server 2003.  Copy this into notepad as save as fixwmi.cmd and then from a command line run c:\fixwmi.cmd.

    It takes several minutes to complete and at points it appears that it is not running but it is.  After it is complete, you see the :END statement start the SQL server installation again and you should be fixed.

     

    FIXWMI.CMD
    ------------------------

    @echo on
    cd /d c:\temp
    if not exist %windir%\system32\wbem goto TryInstall
    cd /d %windir%\system32\wbem
    net stop winmgmt
    winmgmt /kill
    if exist Rep_bak rd Rep_bak /s /q
    rename Repository Rep_bak
    for %%i in (*.dll) do RegSvr32 -s %%i
    for %%i in (*.exe) do call :FixSrv %%i
    for %%i in (*.mof,*.mfl) do Mofcomp %%i
    net start winmgmt
    goto End

    :FixSrv
    if /I (%1) == (wbemcntl.exe) goto SkipSrv
    if /I (%1) == (wbemtest.exe) goto SkipSrv
    if /I (%1) == (mofcomp.exe) goto SkipSrv
    %1 /RegServer

    :SkipSrv
    goto End

    :TryInstall
    if not exist wmicore.exe goto End
    wmicore /s
    net start winmgmt
    :End

  • Friday, February 10, 2006 4:16 PMSteve R1 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I was also receiving a WMI configuration error when trying to install SQL Server 2005 Standard Edition that was distributed by Microsoft during the Ready To Launch tour.  Running the batch file above fixed my WMI configuration issue.  Thanks!
  • Monday, March 20, 2006 6:03 AMvailyve Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Many thanks for this wonderful script I must say.

    My internet explorer XP SP2 would not let me go any further than logon and password authentication pages on some web sites. (like www.ewiz.com and others...)

    After trying every possilbe wiht the settings under the tools menu no luck, I was about to reinstall the whole XP...until this script fixed it all...

    Thank you!

     

     

  • Sunday, April 16, 2006 8:31 PMBryan.Edwards Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    This information was perfect.

    I have been looking for the past week, trying to get SQL express to install

    Thanks !!!!!!!!

  • Saturday, April 29, 2006 9:42 PMTP Diffenbach Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    For whatever reason, copying and pasting this script pasted in unicode rather than ascii. This made the cmd parser barf. To convert it from unicode to ascii (on Windows 200 or XP), use the "type" command redirected to a file, e.g,

    type original.in.unicode.bat > ascii.copy.bat

    Then run the new batch file.

    (As it turns out, my problem wasn't with the WMI configuration, but that I'd told my application firewall to deny WMI run permissions.)

  • Wednesday, May 17, 2006 7:55 AMStefan Grossmann Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi,

     

    i also have the wmi problem. Then i also wanted to put the script onto the server to fix the wmi. But as soon as i copy the file, it is directly deleted by f-secure, which thinks that the script is a trojan.

     

    Any suggestions,

     

    thx in advance.

  • Wednesday, May 17, 2006 8:47 AMAndreas Johansson Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Rename the file to txt, copy it, rename back to cmd.

    If f-secure still catches that, just disable it and copy the cmd file as is.

     

  • Wednesday, June 07, 2006 3:31 PMVicki Johnson Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I have tried this script several times, with no effect.  I have administrator privileges and although I get the same error mentioned by I Mrus, the the LocalSystem account is affected.  Beyond having admin authority and having the script (I run it, reboot, install SQL Srver Express; when fails, uninstall with Add/Remove programs) what can be done to correct this.  Below is a sample of the Application error from Computer Mangement:

    Event Type: Warning
    Event Source: WinMgmt
    Event Category: None
    Event ID: 63
    Date:  6/7/2006
    Time:  1:03:47 AM
    User:  MY_NOTEBOOK\Owner
    Computer: MY_NOTEBOOK
    Description:
    A provider, HiPerfCooker_v1, has been registered in the WMI namespace, Root\WMI, to use the LocalSystem account.  This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    BTW - the link is dead.

    Any ideas?

  • Thursday, July 20, 2006 6:34 PMStephajn Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I just wanted to add to this thread to say that the script also worked for me.

     

    Thanks so much for that!

  • Wednesday, August 16, 2006 9:06 AMsk49 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I have just run that script and then launched the SQLEXPR_ADV.EXE again, and I still receive this error with the usual WMI configuration message:

    Error:  70346 (0x112ca).

    Windows XP SP2 fully updated from Microsoft Updates.

  • Tuesday, September 12, 2006 3:18 AMW. Shawn Boone Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Thank you for this. God Bless.
  • Saturday, September 16, 2006 6:57 PMsk49 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Any idea why the script has not corrected this issue on my laptop?

    Dell Lattitude D620

    XP SP2 fully updated

  • Saturday, January 20, 2007 4:33 PMJuney Moon Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Tried it.  Worked just as you said.  thanks

  • Wednesday, January 24, 2007 8:51 PMrichard12345 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Thanks - it worked for me despite Microsoft's on line help checker saying the problem was unknown.
  • Wednesday, January 31, 2007 5:58 PMmmeier Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Any other suggestions? Ran this and I am still getting the errors when I try to install or uninstall SQL.
  • Saturday, February 24, 2007 11:20 PMSebastian Dhom Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi,

    ich have encountered the same error and the script has not fixed it.

    BUT: As I called the script the second time, it seems to work....

     

     

  • Thursday, March 01, 2007 6:05 AMa abiMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Thanks, really the .cmd script helped me out. It took several hours for some strange reason on a pretty fast sever, but I could reinstall SQL Server and now everything works again
  • Sunday, March 04, 2007 4:00 AMJohninLux Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Had the same problem which has taken roughly 4 hours away from my life, just fixed it. I used the fixwmi.cmd - no result (at least not immediate, if at all). Tried services.msc and started every service that looked remotely connected to WMI, RPC and/or SQL that was not running. I cannot tell you which service I started that worked (as my OS is French, and the services do not have the same name in English - I look for the keywords).
  • Thursday, March 22, 2007 8:06 AMAnders Hammarsten Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    My attempts to install the batch file failed. It appears in an oscillating mode on the screen no matter for how long it runs. No confirmation of succeeded installation follows. Any suggestions?
  • Wednesday, April 04, 2007 6:44 PMIsaac Shloss Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I think I found a fix.  I have SP1 which introduced a ton of new DCOM settings.  I granted the network service and local service accounts local launch permissions in DCOM's machine-limit's settings.
  • Monday, April 16, 2007 1:50 PMchaitra1 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    that's gr8 answer
  • Monday, April 23, 2007 12:32 PMJonasFagerberg Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi,

    I solved this by uninstalling the following programs and reinstallig them in the specified order. I did not have to run the script.

    1. WindowsInstaller Svensk.exe
    2. dotnetfx.exe (Framework 2.0)
    3. SQLEXPR_SVE.EXE (SQL Server 2005 Express)
    4. msxml6.msi
    5. SQLServer2005_SSMSEE.msi (Sql Server 2005 Express Management Studio Express)

    /Jonas

  • Wednesday, April 25, 2007 5:49 PMofúnillo Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Gracias. Thanks. WMI ya no da error

     

    FIXWMI.CMD

     

    me funcionó para resolver el problema

  • Wednesday, August 29, 2007 7:12 PMdouglaswhittington Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Failed to solve the problem on my Dell Latitude 820.
    I notice another post says failed on Dell Latitude 620.

    I appreciate the effort.  thanks.
  • Thursday, August 30, 2007 1:51 PMfarukozturk Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     

    Hi,

     

    I run this batch but I am still getting same error. Do you have any idea?

     

    Thanks

     

    OS XP Pro SP2

    1 Gb of Ram

  • Wednesday, October 10, 2007 4:26 PMtbroas Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I tried the scrip(I'm running Vista Home Premium) and I get the following errors,  any ideas on how I can fix them?

     

     

     

    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 15 -
     18:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp wmipcima.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: wmipcima.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 7 -
    12:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp wmipdfs.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: wmipdfs.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 7 -
    12:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp wmipdskq.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: wmipdskq.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 7 -
    12:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp WmiPerfClass.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: WmiPerfClass.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 15 -
     22:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp WmiPerfInst.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: WmiPerfInst.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 15 -
     21:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp wmipicmp.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: wmipicmp.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp wmipiprt.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: wmipiprt.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 7 -
    12:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp wmipjobj.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: wmipjobj.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 7 -
    14:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp wmipsess.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: wmipsess.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 7 -
    12:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp wmitimep.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: wmitimep.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 6 -
    18:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp WMI_Tracing.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: WMI_Tracing.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 15 -
     28:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp wmp.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: wmp.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 14 -
     155:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp wmpnetwk.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: wmpnetwk.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 11 -
     72:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp wpc.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: wpc.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 14 -
     51:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp wpcsprov.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: wpcsprov.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 5 -
    8:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp wpcuninst.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: wpcuninst.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 5 -
    8:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp wpdbusenum.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: wpdbusenum.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 14 -
     87:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp wpdfs.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: wpdfs.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 14 -
     87:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp wpdmtp.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: wpdmtp.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 14 -
     95:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp wpdshext.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: wpdshext.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 14 -
     99:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp WPDShServiceObj.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: WPDShServiceObj.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 14 -
     95:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp wpdsp.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: wpdsp.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 14 -
     95:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp wpdwcn.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: wpdwcn.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 14 -
     55:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp wpd_ci.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: wpd_ci.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 14 -
     95:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp wscenter.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: wscenter.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 5 -
    8:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp wscmisetup.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: wscmisetup.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 14 -
     39:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp WSDApi.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: WSDApi.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 15 -
     84:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp WsmAuto.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: WsmAuto.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 14 -
     147:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp WUDFx.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: WUDFx.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 16 -
     181:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp WUDFxUninstall.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: WUDFxUninstall.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp wzcdlg.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: wzcdlg.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 10 -
     27:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>Mofcomp xwizards.mof
    Microsoft (R) MOF Compiler Version 6.0.6000.16386
    Copyright (c) Microsoft Corp. 1997-2006. All rights reserved.
    Parsing MOF file: xwizards.mof
    MOF file has been successfully parsed
    Storing data in the repository...
    An error occurred while opening the namespace for object 1 defined on lines 14 -
     39:
    Error code: 0x8004100ACompiler returned error 0x8004100a
    C:\Windows\System32\wbem>net start winmgmt
    System error 5 has occurred.

    Access is denied.


    C:\Windows\System32\wbem>goto End

    C:\Windows\System32\wbem>

     

     

  • Wednesday, October 17, 2007 2:09 PMColSchmoll Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Unfortunately it didn't work for me, I still get eh following errors from WMIDiag.vbs - anyone help?

    33373 14:59:50 (0) ** WMI QUALIFIER access operations: .................................................................................... OK.
    33374 14:59:50 (1) !! ERROR: WMI ENUMERATION operation errors reported: ................................................................... 16 ERROR(S)!
    33375 14:59:50 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_Cache', 0x80004002 - No such interface supported.
    33376 14:59:50 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33377 14:59:50 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_Memory', 0x80004002 - No such interface supported.
    33378 14:59:50 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33379 14:59:50 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_Objects', 0x80004002 - No such interface supported.
    33380 14:59:50 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33381 14:59:50 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_PagingFile', 0x80004002 - No such interface supported.
    33382 14:59:50 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33383 14:59:50 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_Processor', 0x80004002 - No such interface supported.
    33384 14:59:50 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33385 14:59:50 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfOS_System', 0x80004002 - No such interface supported.
    33386 14:59:50 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33387 14:59:50 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfProc_Process', 0x80004002 - No such interface supported.
    33388 14:59:50 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33389 14:59:50 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_PerfProc_Thread', 0x80004002 - No such interface supported.
    33390 14:59:50 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33391 14:59:50 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_ICMP', 0x80004002 - No such interface supported.
    33392 14:59:50 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33393 14:59:50 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_ICMPv6', 0x80004002 - No such interface supported.
    33394 14:59:50 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33395 14:59:50 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_IPv4', 0x80004002 - No such interface supported.
    33396 14:59:50 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33397 14:59:50 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_IPv6', 0x80004002 - No such interface supported.
    33398 14:59:50 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33399 14:59:50 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_TCPv4', 0x80004002 - No such interface supported.
    33400 14:59:50 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33401 14:59:50 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_TCPv6', 0x80004002 - No such interface supported.
    33402 14:59:50 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33403 14:59:50 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_UDPv4', 0x80004002 - No such interface supported.
    33404 14:59:50 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33405 14:59:50 (0) ** - Root/CIMV2, InstancesOf, 'Win32_PerfFormattedData_Tcpip_UDPv6', 0x80004002 - No such interface supported.
    33406 14:59:50 (0) **   MOF Registration: 'C:\WINDOWS\SYSTEM32\WBEM\WMIPERFINST.MOF'
    33407 14:59:50 (0) **
    33408 14:59:50 (0) ** WMI EXECQUERY operations: ........................................................................................... OK.
    33409 14:59:50 (0) ** WMI GET VALUE operations: ........................................................................................... OK.
    33410 14:59:50 (0) ** WMI WRITE operations: ............................................................................................... NOT TESTED.
    33411 14:59:50 (0) ** WMI PUT operations: ................................................................................................. NOT TESTED.
    33412 14:59:50 (0) ** WMI DELETE operations: .............................................................................................. NOT TESTED.
    33413 14:59:50 (0) ** WMI static instances retrieved: ..................................................................................... 1645.
    33414 14:59:50 (0) ** WMI dynamic instances retrieved: .................................................................................... 0.
    33415 14:59:50 (0) ** WMI instance request cancellations (to limit performance impact): ................................................... 1.
    33416 14:59:50 (0) ** ----------------------------------------------------------------------------------------------------------------------------------
    33417 14:59:50 (0) ** # of Event Log events BEFORE WMIDiag execution since the last 20 day(s):
    33418 14:59:50 (0) **   DCOM: ............................................................................................................. 0.
    33419 14:59:50 (0) **   WINMGMT: .......................................................................................................... 0.
    33420 14:59:50 (0) **   WMIADAPTER: ....................................................................................................... 0.
    33421 14:59:50 (0) **
    33422 14:59:50 (0) ** # of additional Event Log events AFTER WMIDiag execution:
    33423 14:59:50 (0) **   DCOM: ............................................................................................................. 0.
    33424 14:59:50 (0) **   WINMGMT: .......................................................................................................... 0.
    33425 14:59:50 (0) **   WMIADAPTER: ....................................................................................................... 0.
    33426 14:59:50 (0) **
    33427 14:59:50 (0) ** 16 error(s) 0x80004002 - (WBEM_UNKNOWN) This error code is external to WMI.
    33428 14:59:50 (0) ** => This error is not a WMI error. It is a DCOM error due to the following reasons:
    33429 14:59:50 (0) **    - An application has changed the COM/DCOM settings of OLE32.DLL and/or OLEAUT32.DLL.
    33430 14:59:50 (0) **    - The registry settings of COM/DCOM has been damage or wrongly modified.
    33431 14:59:50 (0) ** => To correct this situation, you must re-register the original COM/DCOM DLLs with REGSVR32.EXE
    33432 14:59:50 (0) **    i.e. 'REGSVR32.EXE OLE32.DLL'
    33433 14:59:50 (0) **    i.e. 'REGSVR32.EXE OLEAUT32.DLL'

     

     

     

  • Wednesday, November 14, 2007 12:17 PMAqeelish Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     

     

    Hay, u deserve kudos ...!

     

    thanx for saving my life ....

  • Friday, February 15, 2008 4:56 PMEmbeddedlinux Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    The Script works fine on XP PRO SP2 Visual Studio 2005

    1. The script takes about 2 to 3 minuites in the middle so it does not finish really quickly don't shut the command window down until after you see end!  (It doesn't work then!)
    2. As it's next trick sql server cannot find the native windows client.  Get winnsqcli.msi ? sp from running (on Visual Studio 2005 d:\wcu\SSE\sqlexpr32.exe /x , then tell it where to expand to as it asks and "REPAIR" the native windows sql client so you don't have to reboot and spoil the installation.
    Other than that small extra trick the installation was slick.

    Then come the updates.

    1. The first time take all the express updates.
    2. Reboot.
    3. Hotfix for visual studio 2005 will fail.
    4. take all the express updates again and you will get the Visual Studio 2005 hotfix again.
    5. This time it takes.
    6. Reboot.
    Decide if you really care to want .net V3 sp1 .net V3, Login Live and silverlight? from the custom updates.  I didn't feel the need.  Your mileage will vary.....

    DONE!  (As of Feb 2008 only!)
  • Thursday, March 13, 2008 4:34 AMmuci Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    C:\>fixwmi.cmd
     
    C:\>cd /d c:\temp
     
    C:\Temp>if not exist C:\WINDOWS\system32\wbem goto TryInstall
     
    C:\Temp>cd /d C:\WINDOWS\system32\wbem
     
    C:\WINDOWS\system32\wbem>net stop winmgmt
    The following services are dependent on the Windows Management Instrume
    ervice.
    Stopping the Windows Management Instrumentation service will also stop
    vices.
     
       Windows Firewall/Internet Connection Sharing (ICS)
       Access Connections Main Service
     
    Do you want to continue this operation? (Y/N) No: y
     
    The Windows Firewall/Internet Connection Sharing (ICS) service was stop
    ssfully.
     
    The Access Connections Main Service service is stopping.
    The Access Connections Main Service service was stopped successfully.
     
    The Windows Management Instrumentation service is stopping.
    The Windows Management Instrumentation service was stopped successfully
     

    C:\WINDOWS\system32\wbem>winmgmt /kill
     
    C:\WINDOWS\system32\wbem>if exist Rep_bak rd Rep_bak /s /q
     
    C:\WINDOWS\system32\wbem>rename Repository Rep_bak
     
    C:\WINDOWS\system32\wbem>for %i in (*.dll) do RegSvr32 -s %i
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s cimwin32.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s CmdEvTgProv.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s dsprov.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s esscli.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s evntrprv.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s fastprox.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s framedyn.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s fwdprov.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s krnlprov.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s mofd.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s msiprov.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s ncprov.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s ntevt.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s policman.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s provthrd.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s repdrvfs.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s smtpcons.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s snmpcl.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s snmpincl.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s snmpsmir.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s snmpstup.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s snmpthrd.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s stdprov.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s tmplprov.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s trnsprov.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s updprov.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s viewprov.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s wbemads.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s wbemcntl.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s wbemcomn.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s wbemcons.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s wbemcore.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s wbemdisp.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s wbemess.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s wbemperf.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s wbemprox.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s wbemsvc.dll
     
    C:\WINDOWS\system32\wbem>RegSvr32 -s wbemupgd.dll
     
    Paused at this point for 3 minuntes
     
    parsgin on these fileds takes place......lots of output
     
    and it worked
     
    BIG Question ---- WHAT THE HECK JUST happened Smile
     
     

     
  • Friday, April 11, 2008 1:13 AMUnyime Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    This is genius, it worked absolutely fine for me even in my virtual pc environment, could you give a brief overview of what was taking place there. Thanks a million .

  • Sunday, May 04, 2008 5:29 PMMuhammad Aamir Iqbal Arain Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Thanxs for this script.It works with ansii encoding.
  • Friday, May 16, 2008 8:34 PMb1gjohn Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Script worked great - saved my arse.

     

  • Thursday, May 22, 2008 4:49 AMRR96815 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Previously tried multiple XP professional reinstalls. This script worked to get SQL install to continue. Got numerous errors on the install which suggest problem with XP installation, but at least I'm past the wmi problem

  • Wednesday, May 28, 2008 11:37 AMJ.Prakash Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi,
    I too got the same error. I executed the batch file and that resolved my issue.
    Thanks for your support.

  • Tuesday, June 17, 2008 4:22 PMneerajaadi Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
     I Mrus wrote:

    Hello PPl,

    I am getting this error again and again.

    The SQL Server System Configuration Checker cannot be executed due to WMI configuration on the machine mymachine Error:2147749896 (0x80041008).

     

    I uninstall all version of Visual Studio 2005 just kept Microsoft .NET Framework 2.0.  Still I am getting this error when I am running SQLEXPR.exe to install the SQL Server 2005 Express.

     

    PLEASE HELP!

     

    Thank you. 

  • Tuesday, June 24, 2008 9:08 PMKenPearson Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Thank you very much.

    SQL 2005 continued to install.

     

    K9

  • Monday, July 07, 2008 7:01 PMTremel Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi bwalkertn

     

    This script worked perfectly the first time of running.

     

    Big thankyou

     

     

    BillH

  • Sunday, July 20, 2008 6:36 PMgauravaorra Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    great.. it was a soul saver.. worked like a charm..
  • Tuesday, July 22, 2008 6:41 AMk srinivas Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    hi,

    this message is realy got helped.if like this any other information on any server like windows 2003 server,sql server,exchange server.pls send me on srini.blr@live.com.

  • Tuesday, August 05, 2008 8:45 PMjaybond Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     

    I dont know what the script did but it worked perfect on my Windows XP SP2. I can now uninstall my Sql server 2005.
  • Monday, August 11, 2008 8:14 PMPandu123 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Thank u ,

     

     

     

    this wos very worth ful solutaion

     

     

     

     

    Regards ,

    Nagaraj.N

     

  • Saturday, October 11, 2008 2:52 PMDrco Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Thank you, thank you thank you.

     

    This was really pissing me off as I was unable to uninstall SQL 2005. Also thanks to the other post regarding unicode versus ascii - the parser had errors until I changed to ascii.

     

    Ronan

     

  • Wednesday, October 15, 2008 5:46 PMRBSRCL Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Worked like a champ!! Thank you!!!

     

  • Friday, October 17, 2008 8:59 PMClemens.Krusche Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I am using Avast-antivirus. When I copied the above text of the command file to my file and tried to save it I got a virus alert
  • Wednesday, November 05, 2008 9:12 PMKo7et2000 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Really it was so nice and it works well

    thx in advance

    and if u can give us the source of this patch ( website ) it will be so nice


  • Sunday, November 23, 2008 10:42 PMmasihm Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

     

  • Tuesday, November 25, 2008 3:48 PMddsgarcia Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Thanks!

     

    I was getting sick of it, looking to fix that problem, bc, I couldn´t install that ***, anyway, great contribution

     

    Arigato!

     

  • Tuesday, February 24, 2009 4:34 PMDamian OBrien Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    THANK YOU!  This worked for me too.

    I was trying to install SQL Management Studio on XP SP3.  I got some dll errors on install (xolehlp.dll and msdtcprx.dll) at first.  I copied these from an XP SP2 install that I had into c:\windows\system32 (I didn't need to regsiter them).

    Then, I hit the WMI problem....I ran the fixwmi.cmd file but ran into errors (missing dll's, mofcomp not recognized...).  I had a system with a working install of SQL Management Studio, so I copied the MISSING files out of the c:\windows\wbem folder into the XP SP3 install.  After running the batch file again, it all worked!

    Thanks again.  This was a pain!
  • Wednesday, April 08, 2009 7:12 AMvenkat3056 Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Thanks mate... It worked for me..I got this error while trying to uninstall SQL Server 2005,,,,After running this script., it worked.
  • Tuesday, June 02, 2009 5:53 AMJezzrel Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi bwalkertn,

    I have encountered also this WMI error, I copied, pasted it to notepad and saved it as fixwmi.cmd the said script and run it, oh man, after a few seconds of running and the script exited. I tried installing MS Sql 2005 and it works...

    Thanks man...


    ~** Strong Fighting Spirit **~
  • Thursday, June 04, 2009 12:16 AMDon Ferguson Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I too am receiving this error.  More specifically it is preventing the installation of new instances and interferring with reporting services.

    The exact error is "Server buffers are full and data cannot be accepted" 0x80041045. 

    Simply rebooting the server will temporarily fix the issue, but this is on a x64 production PolyServe machine and the PolyServe service has a dependancy on the WINMGMT (WMI) service.  So stopping the service as needed is not an option.  I did run WMIDIAG and it shows the following:

    .1832 15:00:00 (1) !! ERROR: WMI EXECQUERY operation errors reported: ..................................................................... 19 ERROR(S)!
    .1833 15:00:00 (0) ** - Root, Select * From __EventConsumer, 0x80041045 - (WBEM_E_SERVER_TOO_BUSY) Call to IWbemObjectSink::Indicate has failed. The provider can refire the event.
    .1834 15:00:00 (0) ** - Root/CIMv2, Select * From Win32_LogicalDisk WHERE FreeSpace > 10000000 AND DriveType = 3, 0x80041045 - (WBEM_E_SERVER_TOO_BUSY) Call to IWbemObjectSink::Indicate has failed. The provider can refire the event.
    .1835 15:00:00 (0) ** - Root/CIMv2, Select DriveType From Win32_LogicalDisk WHERE Name='C:', 0x80041045 - (WBEM_E_SERVER_TOO_BUSY) Call to IWbemObjectSink::Indicate has failed. The provider can refire the event.
    .1836 15:00:00 (0) ** - Root/CIMv2, Select * From Win32_Service, 0x80041045 - (WBEM_E_SERVER_TOO_BUSY) Call to IWbemObjectSink::Indicate has failed. The provider can refire the event.
    .1837 15:00:00 (0) ** - Root/CIMv2, Select * From Win32_PageFileUsage, 0x80041045 - (WBEM_E_SERVER_TOO_BUSY) Call to IWbemObjectSink::Indicate has failed. The provider can refire the event.
    .1838 15:00:00 (0) ** - Root/CIMv2, Select * From Win32_BIOS WHERE Version IS NOT NULL, 0x80041045 - (WBEM_E_SERVER_TOO_BUSY) Call to IWbemObjectSink::Indicate has failed. The provider can refire the event.
    .1839 15:00:00 (0) ** - Root/CIMv2, Select * From Win32_NetworkAdapter WHERE AdapterType IS NOT NULL AND AdapterType != "Wide Area Network (WAN)" AND Description != "Packet Scheduler Miniport", 0x80041045 - (WBEM_E_SERVER_TOO_BUSY) Call to IWbemObjectSink::Indicate has failed. The provider can refire the event.
    .1840 15:00:00 (0) ** - Root/CIMv2, Select * From Win32_Processor WHERE Name IS NOT NULL, 0x80041045 - (WBEM_E_SERVER_TOO_BUSY) Call to IWbemObjectSink::Indicate has failed. The provider can refire the event.
    .1841 15:00:00 (0) ** - Root/CIMv2, Select * From Win32_DiskDrive, 0x80041045 - (WBEM_E_SERVER_TOO_BUSY) Call to IWbemObjectSink::Indicate has failed. The provider can refire the event.
    .1842 15:00:00 (0) ** - Root/CIMv2, Select * From Win32_ComputerSystem, 0x80041045 - (WBEM_E_SERVER_TOO_BUSY) Call to IWbemObjectSink::Indicate has failed. The provider can refire the event.
    .1843 15:00:00 (0) ** - Root/CIMv2, Select * From Win32_DiskPartition, 0x80041045 - (WBEM_E_SERVER_TOO_BUSY) Call to IWbemObjectSink::Indicate has failed. The provider can refire the event.
    .1844 15:00:00 (0) ** - Root/CIMv2, Select * From Win32_LogicalDisk WHERE Description != "Network Connection", 0x80041045 - (WBEM_E_SERVER_TOO_BUSY) Call to IWbemObjectSink::Indicate has failed. The provider can refire the event.
    .1845 15:00:00 (0) ** - Root/CIMv2, Select * From Win32_VideoController, 0x80041045 - (WBEM_E_SERVER_TOO_BUSY) Call to IWbemObjectSink::Indicate has failed. The provider can refire the event.
    .1846 15:00:00 (0) ** - Root/CIMv2, Select * From Win32_USBController, 0x80041045 - (WBEM_E_SERVER_TOO_BUSY) Call to IWbemObjectSink::Indicate has failed. The provider can refire the event.
    .1847 15:00:00 (0) ** - Root/CIMv2, Select * From Win32_DesktopMonitor, 0x80041045 - (WBEM_E_SERVER_TOO_BUSY) Call to IWbemObjectSink::Indicate has failed. The provider can refire the event.
    .1848 15:00:00 (0) ** - Root/CIMv2, Select * From Win32_PointingDevice WHERE Status = "OK", 0x80041045 - (WBEM_E_SERVER_TOO_BUSY) Call to IWbemObjectSink::Indicate has failed. The provider can refire the event.
    .1849 15:00:00 (0) ** - Root/CIMv2, Select * From Win32_Keyboard, 0x80041045 - (WBEM_E_SERVER_TOO_BUSY) Call to IWbemObjectSink::Indicate has failed. The provider can refire the event.
    .1850 15:00:00 (0) ** - Root/CIMv2, Select * From Win32_SystemDriver WHERE StartMode != "Disabled", 0x80041045 - (WBEM_E_SERVER_TOO_BUSY) Call to IWbemObjectSink::Indicate has failed. The provider can refire the event.
    .1851 15:00:00 (0) ** - Root/WMI, Select * From MSNdis_MediaConnectStatus, 0x80041045 - (WBEM_E_SERVER_TOO_BUSY) Call to IWbemObjectSink::Indicate has failed. The provider can refire the event.

    Is there a way too fix this that doesn't involve shutting down the WMI service?
     
  • Thursday, June 04, 2009 12:20 AMDon Ferguson Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    The C:\WINDOWS\system32\wbem>RegSvr32 -s wbemupgd.dll command will actually shutdown the WINMGMT (WMI) service as well as anything that depends on the service.

  • Wednesday, August 05, 2009 7:37 AMAravindPC Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Thanks a lot for the script.
    It worked for me. 
    NB : For others :- chk the appropriate dll s and registry entry before u run the script.
  • Wednesday, September 23, 2009 11:30 PMDJMAYCO Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Thanks!  This worked for a test VM I was setting up. I received the error after I had uninstalled applications and SQL to start with a clean install!
    D