The CoCreateInstance function may return an HRESULT failure on a Windows XP Professional Service Pack 2-based or Windows Server 2003-based computer

The CoCreateInstance function may return an HRESULT failure on a Microsoft Windows XP Professional Service Pack 2 (SP2)-based or Microsoft Windows Server 2003-based computer. The CoCreateInstance function may return one of the following HRESULT values:

• E_HANDLE
• E_NOINTERFACE
• E_ACCESSDENIED

This problem may occur if a remote procedure call (RPC) communication thread that is used for DCOM cross-process communication is ended prematurely on the computer.

For example, this problem may occur in the following scenario:

• A DCOM client thread has an outstanding call to a DCOM server.
• The client process closes before the threads can correctly clean up and call the CoUninitialize function.

In this scenario, another unrelated DCOM process may be prematurely and incorrectly cleaned up by the Remote Procedure Call service. Therefore, E_HANDLE, E_NOINTERFACE, or E_ACCESSDENIED errors occur in the calls that then try to use that DCOM process. When these errors occur, the DCOM server may continue to run on the computer. However, the DCOM server is now inaccessible by other DCOM processes.

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Windows XP Professional SP2 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 this specific problem. 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

There are no prerequisites.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previous hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2003 hotfix information

Prerequisites

There are no prerequisites.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previous hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2003, 32-bit versions

Windows Server 2003, Itanium-based versions

Windows Server 2003, x64-based versions

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

This problem was first corrected in Windows Server 2003 Service Pack 2.

For more information, click the following article number to view the article in the Microsoft Knowledge Base: