Export (0) Print
Expand All

Network Name Resource Availability

Updated: November 25, 2009

Applies To: Windows Server 2008 R2

In a cluster, a Network Name resource can be important because other resources depend on it. A Network Name resource can come online only if it is configured correctly, and is supported correctly by available networks and network configurations.

Events

Event ID Source Message

1050

Microsoft-Windows-FailoverClustering

Cluster network name resource '%1' cannot be brought online because name '%2' matches this cluster node name. Ensure that network names are unique.

1051

Microsoft-Windows-FailoverClustering

Cluster network name resource '%1' cannot be brought online. Ensure that the network adapters for dependent IP address resources have access to at least one DNS server. Alternatively, enable NetBIOS for dependent IP addresses.

1052

Microsoft-Windows-FailoverClustering

Cluster Network Name resource '%1' cannot be brought online because the name could not be added to the system. The associated error code is stored in the data section.

1116

Microsoft-Windows-FailoverClustering

Cluster network name resource '%1' failed to renew its DNS registration. Ensure that the network adapters for dependent IP address resources have access to at least one DNS server. Alternatively, enable NetBIOS for dependent IP addresses. It is possible that the DNS server may be temporarily unavailable - the DNS registration attempt will be retried.

1119

Microsoft-Windows-FailoverClustering

Cluster network name resource '%1' failed to register DNS name '%2' over adapter '%4' for the following reason:

'%3'

1149

Microsoft-Windows-FailoverClustering

The DNS Host (A) and Pointer (PTR) records associated with Cluster resource '%1' were not removed from the resource's associated DNS server. If necessary, they can be deleted manually. Contact your DNS administrator to assist with this effort.

1150

Microsoft-Windows-FailoverClustering

The removal of the DNS Pointer (PTR) record '%2' for host '%3' which is associated with the cluster network name resource '%1' failed with error '%4'. If necessary, the record can be deleted manually. Contact your DNS administrator for assistance.

1151

Microsoft-Windows-FailoverClustering

The removal of the DNS Host (A) record '%2' associated with the cluster network name resource '%1' failed with error '%3'. If necessary, the record can be deleted manually. Contact your DNS administrator for assistance.

1191

Microsoft-Windows-FailoverClustering

Cluster network name resource '%1' failed to delete its associated computer object in domain '%2'. The error code was '%3'.
Please have a domain administrator manually delete the computer object from the Active Directory domain.

1192

Microsoft-Windows-FailoverClustering

Cluster network name resource '%1' failed to delete its associated computer object in domain '%2' for the following reason:
%3.

Please have a domain administrator manually delete the computer object from the Active Directory domain.

1195

Microsoft-Windows-FailoverClustering

Cluster network name resource '%1' failed registration of one or more associated DNS name(s). The error code was '%2'. Ensure that the network adapters associated with dependent IP address resources are configured with access to at least one DNS server.

1196

Microsoft-Windows-FailoverClustering

Cluster network name resource '%1' failed registration of one or more associated DNS name(s) for the following reason:
%2.

Ensure that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.

1211

Microsoft-Windows-FailoverClustering

Cluster network name resource '%1' cannot be brought online. Attempt to locate a writeable domain controller (in domain %2) in order to create a computer object associated with the resource failed. The error code was '%3'. Ensure that a writeable domain controller is accessible to this node within the configured domain.

1212

Microsoft-Windows-FailoverClustering

Cluster network name resource '%1' cannot be brought online. Attempt to locate a writeable domain controller (in domain %2) in order to create a computer object associated with the resource failed for the following reason:
%3.

The error code was '%4'. Ensure that a writeable domain controller is accessible to this node within the configured domain.

1213

Microsoft-Windows-FailoverClustering

Cluster network name resource '%1' could not completely rename the associated computer object in domain '%2'. Attempting to rename the computer object back to its original name '%3' has also failed. The error code was '%4'. This may affect client connectivity until the network name and its associated computer object name are consistent. Either set the network name resource back to the original name '%3' or contact your domain administrator to manually rename the computer object. If the network name and its associated computer object name are still not consistent the next time the resource is brought online, an attempt will be made to create a new consistently named computer object.

1214

Microsoft-Windows-FailoverClustering

Cluster Network Name resource '%1' cannot be brought online because the name could not be added to the system for the following reason: %2.

1215

Microsoft-Windows-FailoverClustering

Cluster network name resource '%1' failed a health check. Network name '%2' is no longer registered on this node. The error code was '%3'. Check for hardware or software errors related to the network adapter. Also, you can run the Validate a Configuration wizard to check your network configuration.

1216

Microsoft-Windows-FailoverClustering

A name change operation on the cluster core netname resource has failed. Attempting to revert the name change operation back to the original name has also failed. The error code was '%1'. You may not be able to remotely manage the cluster using the cluster name until this situation has been manually corrected.

1218

Microsoft-Windows-FailoverClustering

Cluster network name resource '%1' failed to perform a name change operation (attempting to change original name '%3' to name '%4'). The computer object could not be found on the domain controller '%2' (where it was created). An attempt will be made to recreate the computer object the next time the resource is brought online. Additionally, please work with your domain administrator to ensure that the computer object exists in the domain.

1219

Microsoft-Windows-FailoverClustering

Cluster network name resource '%1' failed to perform a name change operation. The domain controller '%2' where computer object '%3' was being renamed, could not be contacted. The error code was '%4'. Ensure the domain controller is accessible and check for connectivity issues. An attempt will be made to recreate the computer object the next time the resource is brought online if the object cannot be found on any domain controller.

1220

Microsoft-Windows-FailoverClustering

The computer account for resource '%1' failed to be renamed from %2 to %3 using Domain Controller %4. The associated error code is stored in the data section.

The computer account for this resource was in the process of being renamed and did not complete. This was detected during the online process for this resource. In order to recover, the computer account must be renamed to the current value of the Name property, i.e., the name presented on the network.

The Domain Controller where the renamed was attempted might not be available; if this is the case, wait for the Domain Controller to be available again. The Domain Controller could be denying access to the account; after resolving access, try to bring the name online again.

If this is not possible, disable and re-enable Kerberos Authentication and an attempt will be made to find the computer account on a different DC. You eed to change the Name property to %2 in order to use the existing CComputer account.

1221

Microsoft-Windows-FailoverClustering

Cluster network name resource '%1' has a name '%2' which does not match the corresponding computer object name '%3'. It is likely that a previous name change of the computer object has not replicated to all domain controllers in the domain. You will be unable to rename the network name resource until the names become consistent. If the computer object has not been recently changed, please contact your domain administrator to rename the computer object and thereby make it consistent. Also, ensure that replication across domain controllers has been successfully completed.

1226

Microsoft-Windows-FailoverClustering

Network Name resource '%1' (with associated network name '%2') has Kerberos Authentication support enabled. Failed to add required credentials to the LSA - the associated error code '%3' indicates insufficient privileges normally required for this operation. The required privilege is 'Trusted Computing Base' and must be locally enabled on each node comprising the cluster.

1227

Microsoft-Windows-FailoverClustering

Network Name resource '%1' (with associated network name '%2') has Kerberos Authentication support enabled. Failed to add required credentials to the LSA - the associated error code is '%3'.

1566

Microsoft-Windows-FailoverClustering

Cluster network name resource '%1' cannot be brought online. The network name resource was terminated by the resource host subsystem because it did not complete an operation in an acceptable time. The operation timed out while performing:
'%2'

1576

Microsoft-Windows-FailoverClustering

Cluster network name resource '%1' failed to register the name '%2' over adapter '%4' in a secure DNS zone. This was due to an existing record with this name and the cluster identity does not have the sufficient privileges to update that record. The error code was '%3'. Please contact your DNS server administrator to verify the cluster identity has permissions on DNS record '%2'.

1577

Microsoft-Windows-FailoverClustering

Cluster network name resource '%1' failed to register the name '%2' over adapter '%4'. The DNS server could not be contacted. The error code was '%3.' Ensure that a DNS server is accessible from this cluster node. The DNS registration will be retried later.

1578

Microsoft-Windows-FailoverClustering

Cluster network name resource '%1' failed to register dynamic updates for name '%2' over adapter '%4'. The DNS server may not be configured to accept dynamic updates. The error code was '%3'. Please contact your DNS server administrator to verify that the DNS server is available and configured for dynamic updates.

Alternatively, you can disable dynamic DNS updates by unchecking the 'Register this connection's addresses in DNS' setting in the advanced TCP/IP settings for adapter '%4' under the DNS tab.

1579

Microsoft-Windows-FailoverClustering

Cluster network name resource '%1' failed to update the DNS record for name '%2' over adapter '%4'. The error code was '%3'. Ensure that a DNS server is accessible from this cluster node and contact your DNS server administrator to verify the cluster identity can update the DNS record '%2'.

1580

Microsoft-Windows-FailoverClustering

Cluster network name resource '%1' failed to register the name '%2' over adapter '%4' in a secure DNS zone. This was due to an existing record with this name and the cluster identity does not have the sufficient privileges to update that record. The error code was '%3'. Please contact your DNS server administrator to verify the cluster identity has permissions on DNS record '%2'.

1589

Microsoft-Windows-FailoverClustering

Cluster network name resource '%1' found one or more IP addresses associated with DNS name '%2' that are not dependent IP address resources. The additional addresses found were '%3'. This may affect client connectivity until the network name and its associated DNS records are consistent. Please contact your DNS server administrator to verify the records associated with name '%2'.

1600

Microsoft-Windows-FailoverClustering

Cluster service failed to set the permissions on the cluster computer object '%1'. Please contact your network administrator to check the cluster security descriptor of the computer object in Active Directory, verify that the DACL is not too big, and remove any unnecessary extra ACE(s) on the object if necessary.

Related Management Information

Network in a Failover Cluster

Failover Clustering

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft