Reseting WMI

Last updated: Friday, June 16, 2006

TOC :: Up

The following article describes how to correct a corrupted WMI repository.

Article Details

Trouble auditing machines using ENT NetCenter or ENT Network monitor typically fall into two categories:

Connection/Security
WMI corruption

Connection/Security problems would usually be indicated by network status codes such as RPC Server Unavailable or Access Denied. In this case, refer to our knowledge base article http://www.microforge.net/kb/36 for further information.

However, if you are unable to audit a machine using our command line auditing utility (EntAudit.exe) then you may have a corrupted WMI repository. A corrupted WMI repository might also be indicated by the following network status codes, when attemptint to audit machines remotely from ENT NetCenter or ENT Network Monitor:

Unknown Error

Error Inspecting Devices

PNP Devices enum error

Specified class does not exist

You may be able to fix this problem by doing one of two things:

Re-registering and recompiling all the WMI providers on the machine concerned
Resetting WMI on the machine concerned

Re-registering and recompiling WMI providers

You can reregister and recompile all of the WMI providers on a particular machine by issueing the following statements from the command prompt in windows:

c:
cd %windir%\system32\wbem\
for %i in (*.dll) do RegSvr32 /s %i
for %i in (*.mof, *.mfl) do Mofcomp %i

Resetting WMI

You can reset WMI on the machine concerned (i.e. the machine that you are unable to audit) by executing the following commands from the command prompt - you could also save these to a batch (*.bat) file that could easily be run on multiple machines:

c:
cd %windir%\system32\wbem\

net stop winmgmt
rmdir /s /q repository
rmdir /s /q Logs
mkdir Logs
net start winmgmt

If after resetting the WMI repository on a machine, you are still unable to audit that machine using our command line auditing utility (EntAudit.exe), please contact Microforge.net Support for further assistance.