After You Start Cluster Administrator, It Appears to Stop Responding

When you start the Cluster Administrator utility, it may appear to stop responding ("hang"). As the resources load, they are listed on the status bar at the bottom of the Cluster Administrator window. The Cluster Administrator utility may stop responding while a particular resource or resource group loads.

Typically, this issue is caused by a particular resource that is in an Online Pending or Offline Pending state. This behavior may occur after you restart the cluster node or after a group has failed over from one cluster node to another.

To work around this issue, use the command-line version of Cluster Administrator (Cluster.exe) to manage the server cluster or wait until all the resources are brought to an Online, Offline, or Failed state.

To view the status of all the resources, run the following command at a command prompt:View the Status column for each resource in the returned results. Note the particular resource that appears to have stopped responding, and then follow the steps in the following Microsoft Knowledge Base article to initiate a failover command by using the Cluster.exe command to force the resource to restart:

Mismatched cluster services files or their associated dynamic link library (DLL) files may also cause the Cluster Administrator to stop responding. This is less likely to occur on Windows Server 2003-based or Windows 2000-based server clusters because of the Windows File Protection (WFP) feature in those operating systems. If the method that is described in the "Workaround" section of this article does not resolve the issue, check the version numbers of the files in the %windir%\Cluster folder and compare them to the versions in the latest service pack or update that you applied.