Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Error 1722 when starting Cluster Administrator


View products that this article applies to.

Symptoms

When you start Cluster Administrator on a computer running Microsoft Cluster Server, the following error message may be displayed:
Windows NT or 2000:
A connection to the cluster at clustername could not be opened. This may be caused by the Cluster Service on node clustername not being started. Would you like Cluster Administrator to attempt to start the Cluster Service on node clustername?
If you click Yes or No, the following error message is displayed:
An error occurred trying to open the cluster at clustername

The RPC server is unavailable.
Error ID: 1722 (0000006ba)
Windows 2003: The Cluster Service on node 'Clustername' cannot be started. The network path was not found. Error ID: -2147024843 (80070035)
After this error message is displayed, it is not possible to connect to the cluster using clustername (where clustername is the name of the cluster server).

↑ Back to the top


Cause

This behavior can occur for either of the following reasons:
  • The Cluster service may not be started.
  • The cluster network name resource may be offline.
    If the parameters of a network adapter on the "Public Network" are changed (for example, when you reinstall a driver, change an IP address, or change a subnet mask), the Cluster service recognizes the network adapter as new. The Cluster service generates a new network for the card and labels it "New Cluster Network." The old Public Network no longer exists, and clustername and the cluster IP address that clustername depends on do not go online.
Note Public Network is the friendly name associated with the interface that network clients use to connect to the cluster. This name may be different in actual deployments because it is user-definable during the installation of Microsoft Cluster Server.

↑ Back to the top


Resolution

To resolve this issue, use the appropriate method.

From one of the nodes of the cluster:
  1. Start Cluster Administrator.
  2. When you are prompted to connect to a cluster, type a period (.) in the Open Connection to Cluster dialog box, and then click Open. At this point, the cluster group is offline.
  3. Click the cluster group, and then click the cluster IP address.
  4. On the File menu, click Properties.
  5. On the Parameters tab, click New Cluster Network in the Network to Use box (the Public Network no longer exists), and then click OK.
  6. Click the cluster IP address.
  7. On the File menu, click Bring Online.
You can now bring the remaining resources online.

If you cannot gain access to one of the nodes of the cluster:
  1. Start Cluster Administrator.
  2. When you are prompted to connect to a cluster, type the NetBIOS name of one of the nodes of the cluster in the Open Connection to Cluster dialog box, and then click Open.
  3. Click the cluster group, and then click the cluster IP address.
  4. On the File menu, click Properties.
  5. On the Parameters tab, click New Cluster Network in the Network to Use box (the Public Network no longer exists), and then click OK.
  6. Click the cluster IP address.
  7. On the File menu, click Bring Online.
You can now bring the remaining resources online.

Note If you created other IP address resources on the cluster, you may have to reassign a network to the IP addresses to bring them online.

↑ Back to the top


Keywords: KB228480, kbprb, kbenv

↑ Back to the top

Article Info
Article ID : 228480
Revision : 6
Created on : 11/1/2006
Published on : 11/1/2006
Exists online : False
Views : 139