Windows Management Instrumentation can't be started

[Pelle]

Ran WMIDiag script.
Says the Wmi system files are there.
7 repository files missing. Can't try to rebuild because I can't restart WMI!

Error: ADAP status: Not available. Tried WMIDiag remedy, i.e.
WINMGMT.EXE /CLEARADAP
WINMGMT.EXE /RESYNCPERF
When I reran WMIDiag.... error still there!!

WMIDiag says the following errors are "These errors are external to WMI"

ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces:
Root, 0x1AD - ActiveX component can't create object.

ERROR: WMI CONNECTION errors occured for the following namespaces:
................................................... 5 ERROR(S)!
..1754 14:06:22 (0) ** - Root, 0x80080005 - Server execution failed.
..1755 14:06:22 (0) ** - Root, 0x80080005 - Server execution failed.
..1756 14:06:22 (0) ** - Root/Default, 0x80080005 - Server execution failed.
..1757 14:06:22 (0) ** - Root/CIMv2, 0x80080005 - Server execution failed.
..1758 14:06:22 (0) ** - Root/WMI, 0x80080005 - Server execution failed.

I used the echo method in "Security Bulletin MS05-051 for COM+ and MS DTC"
(Article: 909444) to make sure the permissions were correct.

Ran sfc /scannow......no problems found!

I've spent a lot of time on this, following links on other forum messages,
reregistering dlls etc. I would rather not have to do a repair install.
Can anyone help? It would be appreciated.
If more info is needed, please ask.
Thanks
Pelle

 

[Mark L. Ferguson]

If you clear the repository folder it will probably start.
...\system32\wbem
(you will have to turn off the winmanagement service to do that)
'net stop winmgmt'

If no help, you can try resetting Permissions.
Aaron Stebner's WebLog Solving setup errors by using the SubInACL tool to
repair file and registry permissions:
http://blogs.msdn.com/astebner/archive/2006/09/04/739820.aspx

--
Was this helpful? Then click the Ratings button. Voting helps the web
interface.
http://www.microsoft.com/wn3/locales/help/help_en-us.htm#RateAPostAsAnswer
Mark L. Ferguson
..

 

[nass]

Ran WMIDiag script.
Says the Wmi system files are there.
7 repository files missing. Can't try to rebuild because I can't restart WMI!

Error: ADAP status: Not available. Tried WMIDiag remedy, i.e.
WINMGMT.EXE /CLEARADAP
WINMGMT.EXE /RESYNCPERF
When I reran WMIDiag.... error still there!!

WMIDiag says the following errors are "These errors are external to WMI"

ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces:
Root, 0x1AD - ActiveX component can't create object.

ERROR: WMI CONNECTION errors occured for the following namespaces:
.................................................. 5 ERROR(S)!
.1754 14:06:22 (0) ** - Root, 0x80080005 - Server execution failed.
.1755 14:06:22 (0) ** - Root, 0x80080005 - Server execution failed.
.1756 14:06:22 (0) ** - Root/Default, 0x80080005 - Server execution failed.
.1757 14:06:22 (0) ** - Root/CIMv2, 0x80080005 - Server execution failed.
.1758 14:06:22 (0) ** - Root/WMI, 0x80080005 - Server execution failed.

I used the echo method in "Security Bulletin MS05-051 for COM+ and MS DTC"
(Article: 909444) to make sure the permissions were correct.

Ran sfc /scannow......no problems found!

I've spent a lot of time on this, following links on other forum messages,
reregistering dlls etc. I would rather not have to do a repair install.
Can anyone help? It would be appreciated.
If more info is needed, please ask.
Thanks
Pelle

Stopping and Starting the WMI Service

If you are experiencing problems with the WMI service you might need to
manually stop and restart the service. Before doing so you should enable
WMI’s verbose logging option. This provides additional information in the WMI
error logs that might be useful in diagnosing the problem. To enable verbose
logging using the WMI control, do the following:
1.Open the Computer Management MMC snap-in and expand Services and
Applications.
2.Right-click WMI Control and click Properties.
3.In the WMI Control Properties dialogue box, on the Logging tab, select
Verbose (includes extra information for Microsoft troubleshooting) and then
click OK.
Alternatively, you can modify the following registry values:
•Set HKEY_LOCAL_MACHINE\Software\Microsoft\WBEM\CIMOM\Logging to 2.
•Set HKEY_LOCAL_MACHINE\Software\Microsoft\WBEM\CIMOM\Logging File Max Size
to 4000000.
After enabling verbose logging try stopping the WMI service by typing the
following
Open a run command prompt:
net stop winmgmt

If the net stop command fails you can force the service to stop by typing
this:
winmgmt /kill

Important. If you are running Windows XP or Windows Server 2003 the WMI
service runs inside a process named Svchost; this process contains other
services as well as WMI. Because of that, you should not try to stop
Svchost;
if you succeed, you’ll stop all the other services running in that process
as
well. Instead, use net stop winmgmt or winmgmt /kill in order to stop just
the WMI service.

You can then restart the service by typing the following command:
net start winmgmt

If the service does not restart try rebooting the computer to see if that
corrects the problem.
If it does not, then continue reading.
MS:: </Quote>

"WMI Diagnosis Utility"
http://www.microsoft.com/technet/scriptcenter/topics/help/wmidiag.mspx

Systems that have changed the default Access Control List permissions on the
%windir%\registration directory may experience various problems after you
install the Microsoft Security Bulletin MS05-051 for COM+ and MS DTC
http://support.microsoft.com/kb/909444
Also you can download the DiagWMI from here and some good solutions on the
page:
http://windowsxp.mvps.org/repairwmi.htm.

= Open a run command and try to re-register these DLLs:
regsvr32 hnetcfg.dll
regsvr32 netcfgx.dll
regsvr32 netman.dll
regsvr32 atl.dll
regsvr32 netshell.dll
Also try repair the WMI as described here:
http://groups.google.com/group/microsoft.public.win32.programmer.wmi/msg/1da6ab3690bc75a0
What Firewall/Anti-Virus you have running on your machine?.
<Ramesh Quote>:

* Insert your Windows XP CD into the drive.

Important note: If you've installed Service Pack 1 or 2, you need to
insert your Windows XP CD (with Service Pack integration, called as the
Slipstreamed Windows XP CD). If you don't have one, you may point to the
%Windir%\ServicePackFiles\i386 folder for the updated DLLs required during
WMI repair. Or, you may create a Slipstreamed XP CD, and insert it when
prompted.

* Click Start, Run and type the following command, and press enter:

rundll32.exe setupapi,InstallHinfSection WBEM 132 %windir%\inf\wbemoc.inf

* Repair process should take few minutes to complete.
Then, restart Windows for the changes to take effect
</End of Quote>
HTH.
Let us know.
nass

 

[Ramesh, MS-MVP]

Hi Pelle,

See section "Comprehensive rebuild method" in this article:

Repairing and re-registering the WMI:
http://windowsxp.mvps.org/repairwmi.htm

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
Windows® Troubleshooting http://www.winhelponline.com
Winhelponline.com blog http://www.winhelponline.com/blog


Ran WMIDiag script.
Says the Wmi system files are there.
7 repository files missing. Can't try to rebuild because I can't restart WMI!

Error: ADAP status: Not available. Tried WMIDiag remedy, i.e.
WINMGMT.EXE /CLEARADAP
WINMGMT.EXE /RESYNCPERF
When I reran WMIDiag.... error still there!!

WMIDiag says the following errors are "These errors are external to WMI"

ERROR: WMI MONIKER CONNECTION errors occured for the following namespaces:
Root, 0x1AD - ActiveX component can't create object.

ERROR: WMI CONNECTION errors occured for the following namespaces:
................................................... 5 ERROR(S)!
..1754 14:06:22 (0) ** - Root, 0x80080005 - Server execution failed.
..1755 14:06:22 (0) ** - Root, 0x80080005 - Server execution failed.
..1756 14:06:22 (0) ** - Root/Default, 0x80080005 - Server execution failed.
..1757 14:06:22 (0) ** - Root/CIMv2, 0x80080005 - Server execution failed.
..1758 14:06:22 (0) ** - Root/WMI, 0x80080005 - Server execution failed.

I used the echo method in "Security Bulletin MS05-051 for COM+ and MS DTC"
(Article: 909444) to make sure the permissions were correct.

Ran sfc /scannow......no problems found!

I've spent a lot of time on this, following links on other forum messages,
reregistering dlls etc. I would rather not have to do a repair install.
Can anyone help? It would be appreciated.
If more info is needed, please ask.
Thanks
Pelle