The Cluster Administrator console may stop responding when it enumerates resources on a Windows Server 2003-based computer

When you try to use the Cluster Administrator console on a Microsoft Windows Server 2003-based computer, the console may not finish its startup. Additionally, you may experience the following symptoms:

• The console stops responding when it enumerates resources in the status bar at the bottom of the user interface.
• If you use cluster commands at a command prompt to administer a server cluster, the cluster commands do not respond.

Note

• At least one instance of the Microsoft Distributed Transaction Coordinator (MS DTC) service is affected by this problem.
• The cluster remains in a functional state, but cannot be managed, even by using the Cluster.exe tool.

This problem occurs because a remote procedure call (RPC) unlock process cannot be completed correctly in Windows Server 2003.

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:

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

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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 tool in Control Panel.

Windows Server 2003, 32-bit versions

Windows Server 2003 with SP1, 32-bit versions

Windows Server 2003, x64-based versions

Windows Server 2003, Itanium-based versions

Windows Server 2003 with SP1, Itanium-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.

Locking mechanisms are implemented by using single-writer, multi-reader (SWMR) locks. When an SWMR lock is unlocked, it does not synchronize correctly. Therefore, all RPC threads in a process must wait for this lock, and the process cannot be recovered. For more information, click the following article number to view the article in the Microsoft Knowledge Base: