Note: In Windows Vista, you need to open an elevated Command Prompt window. To do so, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
Type this command and press Enter: net stop winmgmt
Using Windows Explorer, rename the folder %windir%\System32\Wbem\Repository. (For example, %windir%\System32\Wbem\Repository_bad). %windir% represents the path to the Windows directory, which is typically C:\Windows.
Switch to Command Prompt window, and type the following and press ENTER after each line:
net start winmgmt
EXIT
For Windows Server 2003
Use the following command to detect and repair a corrupted WMI Repository:
rundll32 wbemupgd, RepairWMISetup
Re-registering the WMI components
The .DLL and .EXE files used by WMI are located in %windir%\system32\wbem. You might need to re-register all the .DLL and .EXE files in this directory. If you are running a 64-bit system you might also need to check for .DLLs and .EXE files in %windir%\sysWOW64\wbem.
To re-register the WMI components, run the following commands at the command prompt:
Log on to the computer that is running Exchange 2003 by using an account that has administrative permissions.
b.
Click Start , click Run , type wmimgmt.msc in the Open box, and then click OK .
c.
In the WMI snap-in, right-click WMI Control (Local) , and then click Properties .
d.
If the WMI service is configured correctly, the WMI Control (Local) Properties dialog box is displayed. When you click the General tab, the operating system version and the WMI version information are displayed.
Step 2: Check the WMI security settings
a.
In the WMI snap-in, click the Security tab.
b.
Expand Root , click MicrosoftExchangeV2 , and then click Security .
c.
Make sure that the inherited permissions resemble the following permissions, and then click OK :
•
Administrators
•
Full permissions
•
Everyone
•
Execute method
•
Provider Write
•
Enable account
•
Local Service
•
Execute method
•
Provider Write
•
Enable account
•
Network Service
•
Execute method
•
Provider Write
•
Enable account
d.
Expand CIMV2 , expand Applications , click Exchange , and then click Security .
e.
Make sure that the inherited permissions resemble the following permissions, and then click OK :
•
Administrators
•
Full permissions
•
Everyone
•
Execute method
•
Provider Write
•
Enable account
•
Local Service
•
Execute method
•
Provider Write
•
Enable account
•
Network Service
•
Execute method
•
Provider Write
•
Enable account
f.
Use Windows Explorer to locate and to right-click the WINNT\SYSTEM32\WBEM folder, and then click Properties .
g.
In the wbem Properties dialog box, click the Security tab.
h.
Make sure that the permissions resemble the following permissions, and then click OK :
•
Administrators
•
Full Control
•
Creator Owner
•
Special Permissions
•
Authenticated Users
•
Read & Execute
•
List Folder Contents
•
Read
•
System
•
Full control
Step 3: Use Wbemtest.exe to check classes and namespaces
a.
Click Start , click Run , type wbemtest in the Open box, and then click OK .
b.
In the Windows Management Instrumentation Tester dialog box, click Connect .
c.
In the Namespace field, type root\cimv2\applications\exchange , and then click Connect .
d.
Click Enum Classes . Do not enter a superclass name. Select the Recursive option, and then click OK .
e.
In the Query Result page, compare these values with the values from another server that is correctly running the same version of Exchange 2003 with the same service packs. These values should be the same.
f.
Click Close .
g.
In the Windows Management Instrumentation Tester dialog box, click Connect .
h.
In the Namespace field, type root\microsoftExchangeV2 , and then click Connect .
i.
Click Enum Classes . Do not enter a superclass name. Select the Recursive option, and then click OK .
j.
In the Query Result page, compare these values with the values from another server that is correctly running the same version of Exchange 2003 with the same service packs. These values should be the same.
k.
Click Close .
l.
Click Enum Instances .
m.
Enter the class name that you want to enumerate, such as Exchange_Server or Exchange_DSAccessDC , and then click OK .
The class name depends on the issue that you want to troubleshoot or to test. You can access the class names in steps 3i and 3j.
Step 4: Register the Exchange 2003 WMI .dll files
the WMI namespaces, and the WMI classes You might use an invalid WMI namespace or an invalid WMI class error message when you check the WMI security settings in step 2. Alternatively, you might use an invalid WMI namespace or an invalid WMI class error message when you use Wbemtest.exe to check the WMI classes and the WMI namespaces in step 3.
If this occurs, you must register the required Exchange 2003 .dll files, and then import the Exchange 2003 namespaces and classes to the WMI repository. To do this, follow these steps:
a.
Click Start , click Run , type cmd in the Open box, and then click OK .
b.
Change to the Exchsrvr\Bin directory.
c.
At the command prompt, type the following commands. Press ENTER after each command.
Note The Msgtrk.mof file is included only in Exchange 2003 and in later versions of Exchange Server. This file is not included in Microsoft Exchange 2000 Server.
f.
Click Start , click Run , type services.msc in the Open box, and then click OK .
g.
In the Services snap-in, right-click Windows Management Instrumentation , and then click Restart .
