MS SQL Cluster Password Change Jobs Fail - Cannot Ensure all Nodes Are in List


Date: March 28, 2015
Revision 1.0


When propagating a service account password change to services clustered with Microsoft Clustering services, the following error is received:

Cannot ensure that all nodes for cluster 'CLUSTER_NAME' are in propagation list; aborting propagation to this system.


There are two possible causes for this particular problem being logged:

  1. Clustered service management in ERPM requires all cluster nodes (active and passive) plus the cluster common node be present in the management set and job when managing clustered services.
  2. The target servers were added using fully qualified domain names (FQDN) or IP addresses rather than simple names (NetBIOS names). The cluster API works with the simple system names of the systems, not with the FQDN.


Case 1:

Ensure that all nodes of the cluster and the common cluster node name are added to the management set and included in the job.

Case 2:

Do not add clustered servers using the FQDN. Add them using the simple name of the servers. The common cluster node must also be added using the simple name.

Applies To
Enterprise Random Password Manager (ERPM)

Was this article helpful?
2 out of 2 found this helpful


Powered by Zendesk