Cluster group that has dependent resources does not fail over on a Windows Server-based computer

Applies to: Windows Server 2012 R2 DatacenterWindows Server 2012 R2 EssentialsWindows Server 2012 R2 Foundation More

Symptoms


Consider the following scenario:

  • You establish a failover cluster, and the clustered servers are running Windows Server 2012 R2, Windows Server 2012, or Windows Server 2008 Service Pack 2.
  • You create three resources (resource A, resource B, and resource C) in a cluster group.
  • Resource B depends on resource A, and resource C depends on resource B.
  • After you bring resource A online, resource A has an "Online" status, resource B has an "Online Pending" status, and resource C has a "Waiting for B to be online" status according to the resource dependencies.
  • Online failure occurs on resource A.
  • The Cluster service detects resource A’s failure, the status of resource B changes to "Offline Due To Provider", and the status of resource C is still "Waiting for B to be online".

In this situation, the status of the cluster group is pending and is not changed to "Offline" as expected. Additionally, Cluster Administrator or the Cluster service cannot fail over the cluster group to another node.

Cause


This issue occurs because resource C is not taken offline. The control mechanism only detects a "Waiting To Come Online" status for the immediate dependent of the failed resource. Additionally, the control mechanism assumes that no more dependent resources are taken offline when it detects the "Offline Due To Provider" status of resource B. Then, the cluster group cannot be failed over to another node because the states of the resources in that cluster group are inconsistent. More specifically, some resources are failed or offline and other resources are waiting for their providers to come online.

More Information


  • This issue may occur when there are more than three resources in the cluster group. To more easily understand the issue, only three resources are selected as an example.
  • Resource A, resource B, and resource C can be located anywhere in a provider-dependent relation. However, the resources must have a direct relation to one another.

Resolution


To resolve this issue in Windows Server 2012 R2, install update 2919355.
To resolve this issue in Windows Server 2012 and Windows Server 2008, install the hotfix that is described in this article.

Update information for Windows Server 2012 R2

For more information about how to obtain update 2919355, click the following article number to view the article in the Microsoft Knowledge Base:
2919355 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 Update April, 2014

Hotfix information for Windows Server 2012 and Windows Server 2008

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 website: 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 one of the following operating systems:
  • Windows Server 2012
  • Windows Server 2008 Service Pack 2 (SP2)
For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

968849 How to obtain the latest service pack for Windows Server 2008

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You might have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information


For more information about software update terminology, 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