Article ID: 903929
Article Last Modified on 10/11/2007
APPLIES TO
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows Server 2003, Standard x64 Edition
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
SYMPTOMS
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.
CAUSE
This problem occurs because a remote procedure call (RPC) unlock process cannot be completed correctly in Windows Server 2003.
RESOLUTION
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:
889100 How to obtain the latest service pack for Windows Server 2003
Hotfix information
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
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Ole32.dll | 5.2.3790.250 | 1,191,936 | 14-Jan-2005 | 08:57 | x86 |
| Rpcproxy.dll | 5.2.3790.141 | 26,112 | 16-Mar-2004 | 03:17 | x86 |
| Rpcrt4.dll | 5.2.3790.394 | 659,968 | 23-Aug-2005 | 03:28 | x86 |
| Rpcss.dll | 5.2.3790.250 | 294,912 | 14-Jan-2005 | 08:57 | x86 |
Windows Server 2003 with SP1, 32-bit versions
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Rpcrt4.dll | 5.2.3790.2514 | 642,048 | 23-Aug-2005 | 03:38 | x86 |
Windows Server 2003, x64-based versions
| File name | File version | File size | Date | Time | Platform | Service branch |
|---|---|---|---|---|---|---|
| Rpcrt4.dll | 5.2.3790.2514 | 1,714,176 | 22-Aug-2005 | 12:50 | x64 | Not Applicable |
| Wrpcrt4.dll | 5.2.3790.2514 | 625,664 | 22-Aug-2005 | 12:50 | x86 | WOW |
Windows Server 2003, Itanium-based versions
| File name | File version | File size | Date | Time | Platform | Service branch |
|---|---|---|---|---|---|---|
| Ole32.dll | 5.2.3790.250 | 3,576,832 | 23-Aug-2005 | 06:10 | IA-64 | Not Applicable |
| Rpcproxy.dll | 5.2.3790.141 | 73,216 | 23-Aug-2005 | 06:10 | IA-64 | Not Applicable |
| Rpcrt4.dll | 5.2.3790.394 | 2,151,424 | 23-Aug-2005 | 06:10 | IA-64 | Not Applicable |
| Rpcss.dll | 5.2.3790.250 | 688,640 | 23-Aug-2005 | 06:10 | IA-64 | Not Applicable |
| Wole32.dll | 5.2.3790.250 | 1,191,936 | 23-Aug-2005 | 06:14 | x86 | WOW |
| Wrpcproxy.dll | 5.2.3790.141 | 26,112 | 23-Aug-2005 | 06:14 | x86 | WOW |
| Wrpcrt4.dll | 5.2.3790.394 | 544,768 | 23-Aug-2005 | 06:14 | x86 | WOW |
Windows Server 2003 with SP1, Itanium-based versions
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Rpcrt4.dll | 5.2.3790.2514 | 2,458,112 | 23-Aug-2005 | 06:14 | IA-64 | SP1 | Not Applicable |
| Wrpcrt4.dll | 5.2.3790.2514 | 625,664 | 23-Aug-2005 | 06:14 | x86 | SP1 | WOW |
STATUS
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.
MORE INFORMATION
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:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional query words: SWMRLock Win2K3 Win2003
Keywords: kbbug kbfix kbqfe kbpubtypekc kbhotfixserver kbwinserv2003sp2fix KB903929
