Cluster Administrator May Not Connect to Local Node But Reports Success (293628)
The information in this article applies to:
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Datacenter Edition
This article was previously published under Q293628 SYMPTOMS After you start a node in a server cluster, start Cluster
Administrator (Cluadmin.exe), and then specify "." to connect to the local
node, you may receive the following error messages: The
Cluster service on node NodeName cannot be started.
An error occurred attempting to open the
cluster at NodeName
The Operation completed
successfully
Error ID: 0 (00000000) CAUSE This issue can occur if this node was evicted while the
node was offline. In Windows Server 2003, changes to the cluster can be queued
up for offline nodes until the next time they join the cluster. If a node is
evicted from the cluster while it is offline, the Cluster service is removed
from that node the next time it attempts to join the cluster. The Cluster
service generates the following error message: Event ID
1070
The node failed to begin the process of joining the server cluster.
The error code was 5052 The 5052 error code means that the cluster
node is not a member of the cluster. RESOLUTION To resolve this issue, designate the cluster name instead
of the local "." option when you start Cluster Administrator. STATUSMicrosoft
has confirmed that this is a problem in the Microsoft products that are listed
at the beginning of this article.
MORE INFORMATION This error message is misleading because it indicates that
the operation was completed successfully.
| Modification Type: | Minor | Last Reviewed: | 1/25/2006 |
|---|
| Keywords: | kberrmsg kbprb KB293628 |
|---|
|