"0x80041002 (WBEM_E_NOT_FOUND)" error code occurs when you try to open a WMI namespace on a computer that is running Windows Server 2003 SP2

When you try to open a Windows Management Instrumentation (WMI) namespace on�a computer that is running Windows Server 2003 Service Pack 2 (SP2), you receive the following error code:Notes

• An example of a namespace is the root\cimv2 or root\rosp namespace.
• Not all "0x80041002 (WBEM_E_NOT_FOUND)" error codes are caused by this problem.

This issue occurs because the�WMI repository is corrupted.�

The WMI service does not handle an item deletion operation for the WMI repository correctly. Therefore, the index tree of the WMI repository is corrupted, and the error code that is mentioned in the "Symptoms" section occurs when you try to open a namespace.

Note�Not all WMI repository corruption issues are caused by this issue.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows Server 2003 Service Pack 2 (SP2).

For more information about how to obtain a Windows Server 2003 service pack or a Windows XP Professional x64 Edition service pack, click the following article number to view the article in the Microsoft Knowledge Base:

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2003 file information notes

• In addition to the files that are listed in these tables, this hotfix also installs an associated security catalog file (KBnumber.cat) that is signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2003

For all supported x64-based versions of Windows Server 2003

For all supported IA-64-based versions of Windows Server 2003

To work around this issue, disable the�Resultant Set of Policy (RSoP) logging policy.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about the Resultant Set of Policy (RSoP) Group Policy settings, view the following Microsoft Tech website: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: