Microsoft KB Archive/257901

= How to Force the Cluster Service to Stop and Cause a Failover =

Article ID: 257901

Article Last Modified on 2/28/2007

-

APPLIES TO


 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows NT Server 4.0 Enterprise Edition
 * Microsoft Cluster Server 1.1

-



This article was previously published under Q257901





SUMMARY
If the Cluster service, Cluster Administrator, or any of the resources managed by Cluster Administrator stops responding (hangs), you may have to stop the Cluster service to cause resources to fail over to the other cluster node and to prevent Cluster Administrator from hanging when you try to start it.

Any process upon which Cluster Administrator is dependent (such as being authenticated by a primary or backup domain controller) can cause Cluster Administrator to stop responding.



MORE INFORMATION
To force the Cluster service to stop, start Task Manager and note the PID number for ***Cluster.exe*** CLUSSVC.EXE on the Processes tab. Then, use the Kill program from the Resource Kit to "kill" the PID number for ***Cluster.exe*** CLUSSVC.EXE. The cluster then fails over to the other node.

Additional query words: MSCS freeze frozen hung failover

Keywords: kbclustering kbhowto KB257901

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.