Select the product you need help with

Random Problems in the RPC Runtime in the Cluster Service

Article ID: 818177 - View products that this article applies to.

Hotfix Download Available

Expand all | Collapse all

SYMPTOMS

The Cluster service may randomly stop working, and exception errors may be written to the Cluster log file.

Back to the top | Give Feedback

CAUSE

This problem is caused by a race condition between two threads in the remote procedure call (RPC) runtime.

Back to the top | Give Feedback

RESOLUTION

Service Pack Information

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

260910

(http://support.microsoft.com/kb/260910/EN-US/ )

How to Obtain the Latest Windows 2000 Service Pack

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.

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, submit a request to 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:

http://support.microsoft.com/contactus/?ws=support

(http://support.microsoft.com/contactus/?ws=support)

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. The English version of this fix has the file attributes (or later) 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.

   Date         Time   Version        Size     File name
   ------------------------------------------------------
   08-Apr-2003  08:19  5.0.2195.6692  994,064  Ole32.dll
   08-Apr-2003  08:19  5.0.2195.6701  432,400  Rpcrt4.dll
   08-Apr-2003  08:19  5.0.2195.6692  239,376  Rpcss.dll

Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.

Back to the top | Give Feedback

MORE INFORMATION

For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:

265173

(http://support.microsoft.com/kb/265173/EN-US/ )

The Datacenter Program and Windows 2000 Datacenter Server Product

Theoretically, this problem might occur in any RPC-enabled program. However, Microsoft has seen this problem occur only in the Cluster service. When this problem occurs, the Cluster service records entries that are similar to these in the Cluster log file:

00000638.000009e8::2003/01/22-13:09:14.672 [CS] Exception. Code = 0xc0000005, Address = 0x77f8765f
00000638.000009e8::2003/01/22-13:09:14.672 [CS] Exception parameters: 0, 4d4c5446, 1003f, ae000000
00000638.000009e8::2003/01/22-13:09:17.187 [CS] CallStack:
00000638.000009e8::2003/01/22-13:09:17.187 [CS] Frame Address
00000638.000009e8::2003/01/22-13:09:17.187 0E50FBE8 77F8765F RtlDosSearchPath_U+000004DF
00000638.000009e8::2003/01/22-13:09:17.187 0E50FD90 77FCC538 RtlSizeHeap+00000BFF
00000638.000009e8::2003/01/22-13:09:17.187 0E50FE94 77D5F186 TowerConstruct+000036BC
00000638.000009e8::2003/01/22-13:09:17.187 000919A8 77D65C8D TowerConstruct+0000A1C3
00000638.000009e8::2003/01/22-13:09:17.203 77D426F8 89ABCDEF 0000:00000000
00000638.000009e8::2003/01/22-13:09:17.203 77D4931A 77D64030 TowerConstruct+00008566
00000638.000009e8::2003/01/22-13:09:17.203 2308418B C2042444 0000:00000000

Other stack traces may be listed in the log. To perform additional analysis, you must obtain a crash dump file of the Cluster service by using a debugger.

Back to the top | Give Feedback