XADM: Cluster Resource Manager May Not Detect an Unavailable Server (817294)

SYMPTOMS

The cluster resource manager may not detect that a server in your cluster is unavailable.

When you view the server cluster log file (Cluster.log) you may notice information that is similar to the following information. This information indicates that the IsAlive polling determined that the cluster node was still responding:

00002f0.00000f38::2002/07/09-17:03:44.564 Microsoft Exchange Information Store <Exchange Information Store Instance - (ServerName)>: [EXRES] calling EcStoreIsServerAlive()

00000740.00001408::2002/07/09-17:03:44.627 [EVT] s_ApiEvPropEvents: Calling into EvpPropPendingEvents, size=776...

00000740.00001408::2002/07/09-17:03:44.627 [EVT] s_ApiEvPropEvents: Called EvpPropPendingEvents...

Additionally, you may notice the following information in the server cluster log file:

000002f0.00000f38::2002/07/09-17:03:45.143 Microsoft Exchange Information Store <Exchange Information Store Instance - (ServerName)>: [EXRES] EcStoreIsServerAlive() returned error 0, fIsAlive=TRUE

00000740.000013bc::2002/07/09-17:03:45.189 [EVT] s_ApiEvPropEvents: Calling into EvpPropPendingEvents, size=788...

00000740.000013bc::2002/07/09-17:03:45.189 [EVT] s_ApiEvPropEvents: Called EvpPropPendingEvents...

RESOLUTION

Cumulative Rollup Information

To resolve this problem, obtain the September 2003 Microsoft Exchange 2000 Server Post-Service Pack 3 (SP3) Rollup. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

824282 September 2003 Exchange 2000 Server Post-Service Pack 3 Rollup

Hotfix Information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Exchange 2000 Server service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

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

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this hotfix 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
   --------------------------------------------------------------
   26-Mar-2003  19:06  6.0.6446.0        139,264  Exres.dll

Note Because of file dependencies, this update requires Exchange 2000 Server Service Pack 3 (SP3). For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

301378 How to Obtain the Latest Exchange 2000 Server Service Pack

MORE INFORMATION

After you apply the fix that this article describes, the default time-out value for IsAlive is changed to 5 minutes. If a remote procedure call (RPC) is unsuccessful for longer than the time-out value, the server fails over to another cluster node. After you apply the fix that this article describes, you can modify this time-out value by editing the registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\Server Busy Retry Limit

The default value (in seconds) is 300 (5 minutes).

For additional information about the terminology that is used to describe Microsoft product updates, click the following article number to view the article in the Microsoft Knowledge Base: