Corresponding roles are stuck in the "Stopping" state after one resource fails on a Windows Server 2012 R2-based cluster

Article translations Article translations
Article ID: 2937621 - View products that this article applies to.
Expand all | Collapse all

Symptoms

On a Windows Server 2012 R2-based cluster, when one resource is in the "Failed" state, the Failover Cluster Manager displays the corresponding node roles as "Stopping." However, the corresponding roles can never be stopped. Additionally, the corresponding group is stuck in the "Stopping" state, and the provider resource is stuck in the "Waiting To Terminate" state.

This issue issues occurs because the system does not move poisoned resources to a separate monitor, and therefore the poisoned resources continue to take down other resources.

Resolution

To resolve this issue, install update 2919355. 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

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

Properties

Article ID: 2937621 - Last Review: April 8, 2014 - Revision: 1.0
Applies to
  • Windows Server 2012 R2 Datacenter
  • Windows Server 2012 R2 Essentials
  • Windows Server 2012 R2 Foundation
  • Windows Server 2012 R2 Standard
Keywords: 
kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2937621

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com