The Cluster Service Detects RPC Errors 1726 and 1722


The Cluster service may detect Remote Procedure Call (RPC) errors 1726 and 1722. The Cluster service uses RPC communications for various purposes such as Global Update Manager (GUM) updates and replicating event messages. This error occurs on Xeon multiprocessor computers.


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 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: 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
30-Aug-2002 03:40 5.0.2195.5985 940,304 Ole32.dll
30-Aug-2002 03:40 5.0.2195.6040 429,328 Rpcrt4.dll
30-Aug-2002 03:40 5.0.2195.5985 186,128 Rpcss.dll


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.

More Information

If the Cluster service detects RPC error 1726 while it is performing a GumSendUpdate operation, it sends a "poison" packet to the node that did not update GUM. The following message is recorded in the cluster log file:
0000083c.00000da0::2002/03/27-08:42:53.408 [GUM] GumSendUpdate: Update on node 1 failed with 1726 when it must succeed
0000083c.00000da0::2002/03/27-08:42:53.408 [GUM] GumpCommFailure 1726 communicating with node 1
0000083c.00000da0::2002/03/27-08:42:53.408 [NM] Received advice that node 1 has failed with error 1726.
0000083c.00000da0::2002/03/27-08:42:53.408 [NM] Banishing node 1 from active cluster membership.
0000083c.00000da0::2002/03/27-08:42:53.408 [RGP] Node 2: RGP Event : 0x8, 0x1, 0x6, 0x0.
0000083c.00000da0::2002/03/27-08:42:53.408 [RGP] Node 2: RGP (re)starting: 0x9, 0x3f09, 0x2, 0xff.
0000083c.00000da0::2002/03/27-08:42:53.408 [RGP] Node 2: RGP masks : 0xc000c000, 0xc000c000, 0xc000c000, 0xc000c000.
0000083c.00000da0::2002/03/27-08:42:53.408 [NM] Holding I/O.
0000083c.00000da0::2002/03/27-08:42:53.408 [RGP] Node 2: RGP Hold all IO : 0x0, 0x0, 0x0, 0x0.
0000083c.00000da0::2002/03/27-08:42:53.408 [RGP] Node 2: Ignorescreen->: 0x3fff, 0xbfff, 0x0, 0x0.
0000083c.00000da0::2002/03/27-08:42:53.408 [RGP] Node 2: RGP Send packets: 0x1, 0xc0000000, 0x0, 0x0.
0000083c.00000da0::2002/03/27-08:42:53.455 [RGP] Node 2: RGP Incoming pkt: 0xbfff, 0x9, 0x1, 0x2.
0000083c.00000da0::2002/03/27-08:42:53.455 [RGP] Node 2: RGP recv pkt : 0x90001, 0x0, 0x0, 0x1.
0000083c.00000da0::2002/03/27-08:42:53.455 [RGP] Node 2: RGP Poison sent : 0x1, 0x0, 0x0, 0x0.
0000083c.00000980::2002/03/27-08:42:53.674 [RGP] Node 2: RGP Send packets: 0x1, 0xc0000000, 0x0, 0x0.
If the Cluster service detects RPC errors 1726 and 1722 while it is propagating an event, the following message is recorded in the cluster log file:
0000083c.00000c30::2002/03/27-08:37:15.084 [EVT] EvpPropPendingEvents: EvPropEvents for node 1 failed. status 1726
0000083c.000012c4::2002/03/27-08:37:16.131 [EVT] s_ApiEvPropEvents: Calling into EvpPropPendingEvents, size=772...
0000083c.000012c4::2002/03/27-08:37:16.131 [EVT] s_ApiEvPropEvents: Called EvpPropPendingEvents...
0000083c.000011a0::2002/03/27-08:37:16.272 [EVT] s_ApiEvPropEvents: Calling into EvpPropPendingEvents, size=856...
0000083c.000011a0::2002/03/27-08:37:16.272 [EVT] s_ApiEvPropEvents: Called EvpPropPendingEvents...
0000083c.000012c4::2002/03/27-08:37:18.615 [EVT] s_ApiEvPropEvents: Calling into EvpPropPendingEvents, size=736...
0000083c.000012c4::2002/03/27-08:37:18.615 [EVT] s_ApiEvPropEvents: Called EvpPropPendingEvents...
0000083c.000011a0::2002/03/27-08:38:16.755 [EVT] s_ApiEvPropEvents: Calling into EvpPropPendingEvents, size=780...
0000083c.000011a0::2002/03/27-08:38:16.755 [EVT] s_ApiEvPropEvents: Called EvpPropPendingEvents...
0000083c.00000c30::2002/03/27-08:38:19.318 [EVT] EvpPropPendingEvents: EvPropEvents for node 1 failed. status 1722

Article ID: 326330 - Last Review: Jun 19, 2014 - Revision: 1