The Cluster Administrator May Incorrectly Report That the Cluster Is Unavailable (278939)


The information in this article applies to:

  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Datacenter Server
  • Microsoft Windows NT Server, Enterprise Edition 4.0
This article was previously published under Q278939

SYMPTOMS

If you stop the Cluster service on the local node by means of either the Services tool or the Cluster Administrator, you may receive the following error message, even though the cluster and its resources are functional on another node in the cluster:
Cluster ClusterName is no longer available

CAUSE

This behavior may occur if your system is connected directly to the local node using the "." option in the Cluster Administrator, instead of the cluster name.

RESOLUTION

To resolve this behavior, before you stop the Cluster service, verify your system's connection in the Cluster Administrator. You can view the connection type in the title bar of the Cluster Administrator window.

If your system is connected to the local node, click File, click Open Connection, and then specify the cluster name.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Modification Type:MinorLast Reviewed:1/26/2006
Keywords:kbClustering kbprb w2000mscs KB278939
©2004 Microsoft Corporation. All rights reserved.