Re: Cannot start WMI

From: "Jim Vierra" <jvierra@xxxxxxx>
Date: Mon, 23 May 2005 19:56:28 -0400

I would start by running "SFC /scannow" and see if any files need replacing. This will also re-register fundamental system DLLs that may have become unregistered or have corrupted registry entries.

This is a routine from Eric Sun at MS. It will re-comp all MOFs that are installed on the machine except for MOFs not stored in WBEM

Please continue the following steps to rebuild the WMI repository.

Disable the Windows Management Instrumentation SERVICE in the services console (services.msc)
Back up the contents in the C:\windows\system32\wbem\Repository\
Clearing the contents of C:\windows\system32\wbem\Repository\
Click Start and click Run
In the Run dialog box, please type CMD
In the Command prompt, please just copy and paste the command below. Run it then.

for %1 in (%systemroot%\system32\wbem\*.mof %systemroot%\system32\wbem\*.mfl) do mofcomp %1

Restart the server.

--
Jim Vierra

"Attila Tajti" <attis@xxxxxxxxxxxxx> wrote in message news:1116777859.705187.148040@xxxxxxxxxxxxxxxxxxxxxxxxxxxx...

>I run into a problem with WMI while trying to find a svchost.exe crash.
> I don't use WMI for anything but I think the failing service might try
> to use it and it fails because WMI is failing too.
>
> I tried a lot of things to reinstall WMI but my problem is after
> deleting the repository WMI doesn't start at all and I can't compile
> any mof/mfl files because they can't create namespaces:
>
> C:\WINDOWS\system32\wbem>mofcomp cimwin32.mof
> Microsoft (R) 32-bit MOF Compiler Version 5.1.2600.2180
> Copyright (c) Microsoft Corp. 1997-2001. All rights reserved.
> Parsing MOF file: cimwin32.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 8 -
> 11:
> Error code: 0x80080005Compiler returned error 0x80080005
> C:\WINDOWS\system32\wbem>
> C:\WINDOWS\system32\wbem>net start winmgmt
> The Windows Management Instrumentation service is starting.
> The Windows Management Instrumentation service could not be started.
>
> A system error has occurred.
>
> System error 126 has occurred.
>
> The specified module could not be found.
>
>
> C:\WINDOWS\system32\wbem>winmgmt /?
>
> C:\WINDOWS\system32\wbem>winmgmt /register
>
>
>
> There were 3 log files in the log dir after clearing it and executing
> the above commands:
>
> wbemprox.log
>
> (Sun May 22 12:53:23 2005.6050921) : Using the principal
> -RPCSS/AttisPC-
> (Sun May 22 12:53:53 2005.6080937) : ConnectViaDCOM, CoCreateInstanceEx
> resulted in hr = 0x80080005
> (Sun May 22 14:49:47 2005.13100937) : Using the principal
> -RPCSS/AttisPC-
> (Sun May 22 14:50:17 2005.13130937) : ConnectViaDCOM,
> CoCreateInstanceEx resulted in hr = 0x80080005
> (Sun May 22 16:47:17 2005.20150937) : Using the principal
> -RPCSS/AttisPC-
> (Sun May 22 16:47:47 2005.20180937) : ConnectViaDCOM,
> CoCreateInstanceEx resulted in hr = 0x80080005
> (Sun May 22 17:11:49 2005.21692968) : Using the principal
> -RPCSS/AttisPC-
> (Sun May 22 17:12:19 2005.21722968) : ConnectViaDCOM,
> CoCreateInstanceEx resulted in hr = 0x80080005
> (Sun May 22 17:57:36 2005.24440468) : Using the principal
> -RPCSS/AttisPC-
> (Sun May 22 17:58:06 2005.24470484) : ConnectViaDCOM,
> CoCreateInstanceEx resulted in hr = 0x80080005
>
>
> mofcomp.log:
>
> (Sun May 22 17:57:33 2005.24436828) : Microsoft (R) 32-bit MOF Compiler
> Version 5.1.2600.2180
> (Sun May 22 17:57:33 2005.24436843) : Copyright (c) Microsoft Corp.
> 1997-2001. All rights reserved.
> (Sun May 22 17:57:33 2005.24436875) : Parsing MOF file: cimwin32.dll
> (Sun May 22 17:57:33 2005.24436953) : cimwin32.dll (1): error SYNTAX
> 0X8004400a: Undefined error
> (Sun May 22 17:57:33 2005.24436953) : Compiler returned error
> 0x8004400a(Sun May 22 17:57:35 2005.24439390) : Microsoft (R) 32-bit
> MOF Compiler Version 5.1.2600.2180
> (Sun May 22 17:57:35 2005.24439406) : Copyright (c) Microsoft Corp.
> 1997-2001. All rights reserved.
> (Sun May 22 17:57:35 2005.24439437) : Parsing MOF file: cimwin32.mof
> (Sun May 22 17:57:36 2005.24440453) : MOF file has been successfully
> parsed
> (Sun May 22 17:57:36 2005.24440468) : Storing data in the repository...
> (Sun May 22 17:58:06 2005.24470531) : An error occurred while opening
> the namespace for object 1 defined on lines 8 - 11:
> (Sun May 22 17:58:06 2005.24470546) : Error code: 0x80080005(Sun May 22
> 17:58:06 2005.24470546) : Compiler returned error 0x80080005
>
> winmgmt.log:
>
> (Sun May 22 18:00:10 2005.24594468) :
> Starting WinMgmt, ProcID = f0, CmdLine = /?(Sun May 22 18:00:25
> 2005.24608765) :
> Starting WinMgmt, ProcID = a80, CmdLine = /reg
>
>
>
> Any ideas what should I do? I googled for hours for fixes but
> nothing helped resolve this issue.
>

Follow-Ups:
- Re: Cannot start WMI
  - From: Attila Tajti

References:
- Cannot start WMI
  - From: Attila Tajti

Prev by Date: Re: root\CIMV2\Win32_Processor
Next by Date: Enable\Disable Hibernate
Previous by thread: Cannot start WMI
Next by thread: Re: Cannot start WMI
Index(es):
- Date
- Thread

Relevant Pages

Cannot start WMI
... I run into a problem with WMI while trying to find a svchost.exe crash. ... I don't use WMI for anything but I think the failing service might try ... MOF file has been successfully parsed ... The Windows Management Instrumentation service could not be started. ...
(microsoft.public.windowsxp.wmi)
Re: SBS2003 Backup ... works, but reports failue ???
... "Ensure the Windows Management Instrumentation service is started", ... there are two WMI lines in the Services listing, ... So what non-running Auto Started service is the Daily Performance Report ...
(microsoft.public.windows.server.sbs)
Re: Event 1090 - Userenv error
... It could be that there is a problem with WMI on your machine. ... Stop the Windows Management Instrumentation service. ... Go to the %SystemRoot%\System32\Wbem\Repository folder. ... you restart the computer". ...
(microsoft.public.windowsxp.help_and_support)