FIX: A cluster resource remains offline after the "Run this resource in a separate Resource Monitor" option is disabled in Windows Server 2008

View products that this article applies to.

Symptoms

Consider the following scenario:

The Failover Clustering feature is installed on servers that are running Windows Server 2008.
You configure a cluster resource to run in a separate resource monitor by selecting the Run this resource in a separate Resource Monitor option.
Later, you disable the Run this resource in a separate Resource Monitor option.

In this scenario, the Failover Cluster service crashes, and the cluster resource remains offline. If you try to check the properties of the cluster resource, you receive the following error message:

Cluster cluster_name has become disconnected

Note This problem occurs only on Windows Server 2008 clusters. This problem does not occur on Windows Server 2003 clusters or on Windows Server 2008 R2 clusters.

↑ Back to the top

Cause

This problem occurs because of a race condition in the Cluster service.

After the Run this resource in a separate Resource Monitor option is disabled, you expect the Resource Hosting Subsystem (RHS) process that hosts the cluster resource to close. You expect the process to close after the Cluster service makes a call to close the cluster resource.

When the race condition occurs, the RHS process closes before it handles the Close function from the Cluster service. Therefore, the Cluster service crashes, and the cluster resource remains offline.

↑ Back to the top

Resolution

To resolve this problem, install this hotfix on all cluster nodes.

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 the problem described in this article. 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:

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.

Prerequisites

To apply this hotfix, you must be running Windows Server 2008 or Windows Server 2008 Service Pack 2 on the computer. Additionally, you must have the Failover Clustering feature installed.

Restart information

You do not have to restart the computer after you apply this hotfix. However, you must restart the Cluster service.

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