http://technet.microsoft.com/en-us/library/ff404265.

aspx

Windows Server 2003, Service Pack 1 If you are experiencing problems on a computer running Windows Server 2003, Service Pack 1, you should first run a consistency check by typing the following from the command prompt: Copy Code

rundll32 wbemupgd, CheckWMISetup

Important. The parameter CheckWMISetup is case-sensitive: it must be typed in exactly as shown. If you type in something else, say, checkwmisetup, the consistency check will fail with the message Missing entry: checkwmisetup. After issuing this command, check the WMI Setup log (%windir%\System32\Wbem\Logs\Setup.log). If you see entries similar to this, then the consistency check has failed: Copy Code

(Wed Oct 12 14:17:14 2005): Failing Connecting to Namespace [root\default] with result [80041002]

Note. If there are no entries for the date on which you ran Wbemupgd that means that no inconsistencies were found. If an inconsistency is discovered, that is indicative of a corrupt Repository. You can then try to repair the Repository by typing the following command from the command prompt (again, the parameter RepairWMISetup is case-sensitive): Copy Code

rundll32 wbemupgd, RepairWMISetup

If the repair command succeeds, you should see an entry similar to this in the Setup log: Copy Code

(Wed Oct 12 14:21:24 2005): ERROR: wbemupgd.dll. The WMI repository has failed to upgrade. The repository has been backed up to C:\Windows\System32\Wbem\Repository.001 and a new one created.
If the repair fails or if your script still does not work then you will need to contact Microsoft Product Support Services. Microsoft Windows XP, Service Pack 2 If you are running Windows XP, Service Pack 2 you can use a single command to detect and repair a corrupted WMI Repository. To do so, type the following from the command prompt (note that the parameter UpgradeRepository is case-sensitive and must be typed exactly as shown): Copy Code

rundll32 wbemupgd, UpgradeRepository

After running UpgradeRepository you can verify the results by looking ay the Setup log. If inconsistencies are detected and if the operating system was able to rebuild the Repository you should see information in Setup.log similar to this: Copy Code

(Wed Oct 12 13:46:36 2005): ======================================================================= ====

(Wed Oct 12 13:46:36 2005): Beginning WBEM Service Pack Installation (Wed Oct 12 13:46:36 2005): Current build of wbemupgd.dll is 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) (Wed Oct 12 13:46:36 2005): Current build of wbemcore.dll is 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) (Wed Oct 12 13:46:52 2005): Inconsistent repository detected; it will be recreated (Wed Oct 12 13:47:33 2005): Wbemupgd.dll Service Security upgrade succeeded (XP SP update). (Wed Oct 12 13:47:33 2005): WBEM Service Pack Installation completed. (Wed Oct 12 13:47:33 2005): ======================================================================= ====
Note. There will probably be other entries in the log as well, but you should specifically look for the ones shown above. If the repair fails or if your script still does not work then you will need to contact Microsoft Product Support Services. Other Versions of Windows Only Windows Server 2003, Service Pack 1 and Windows XP, Service Pack 2 include built-in commands for rebuilding the WMI Repository. On other versions of Windows you can rebuild the Repository by doing the following:

1.
2.

Stop the WMI service. (Type net stop winmgmt) from the command prompt.) Rename the folder %windir%\System32\Wbem\Repository. (For example, %windir %\System32\Wbem\Repository_bad.) By renaming the folder the operating system will no longer be able to find the WMI Repository. As a result, it will automatically rebuild the Repository the next time it needs to access WMI information. Restart the WMI service (net start winmgmt) and try your script again.

3.

If your script still fails, try manually rebuilding the repository using the steps described in the section of this document titled Im getting an error regarding provider registration. Suppose this fixes the problem? If your have rebuilt the Repository and your script now works, you might consider the following. Stop the WMI service and rename the current Repository folder (for example, Repository_good), then make Repository_bad the Repository once more (by renaming it back to Repository). Restart the WMI service and see if the script works. If it does not, then simply make Repository_good the WMI Repository once more. Why would you do something like this? Well, as we noted, there are some risks inherent in rebuilding the Repository. For example, you might have applications that only update the Repository during installation; these applications do not have or use MOF files. If you rebuild the Repository then WMI data for those applications will be lost, at least until you re-install the programs. Likewise, you might have permanent event consumers or other types of data that are stored in the Repository; when the Repository is rebuilt that data will be lost. If you can use the old Repository you will save yourself from data loss like this.

Ive rebuilt the WMI Repository and my script still doesnt work
What if youve tried all the steps in this document and WMI still does not work? In that case, you will need to contact Microsoft Product Support Services (PSS). Please make sure you know:

The operating system on which the problem occurred. The latest service pack installed on the computer. Whether or not the operating system is the client or server version (e.g., Windows 2000 Professional vs. Windows 2000 Server). The type of hard drive (IDE or SCSI) on which the operating system is installed.