FAILOVER CLUSTERING

A failover cluster is a group of independent computers that work together to increase the availability of applications and services. If one of the clustered servers fails, another server begins to provide service (a process known as failover).

Hierarchy of Managed Entities

Failover Clustering

Active Directory Permissions for Cluster Accounts
Updated: November 25, 2009

When you create a new clustered service or application, a computer object (computer account) for that clustered service or application must be created in the Active Directory domain. This computer object is created by the computer object of the cluster itself. If the computer object of the cluster itself does not have the appropriate permissions, it cannot create or update the computer object for the clustered service or application.

Event ID

Source

Message

1193
Microsoft-Windows-FailoverClustering Cluster network name resource ‘%1′ failed to create its associated computer object in domain ‘%2′ for the following reason: %3.

The associated error code is: %5

Please work with your domain administrator to ensure that:
- The cluster identity ‘%4′ can create computer objects. By default all computer objects are created in the ‘Computers’ container; consult the domain administrator if this location has been changed.
- The quota for computer objects has not been reached.
- If there is an existing computer object, verify the Cluster Identity ‘%4′ has ‘Full Control’ permission to that computer object using the Active Directory Users and Computers tool.

1194
Microsoft-Windows-FailoverClustering Cluster network name resource ‘%1′ failed to create its associated computer object in domain ‘%2′ for the following reason: %3.

The text for the associated error code is: %4

Please work with your domain administrator to ensure that:
- The cluster identity ‘%5′ can create computer objects. By default all computer objects are created in the ‘Computers’ container; consult the domain administrator if this location has been changed.
- The quota for computer objects has not been reached.
- If there is an existing computer object, verify the Cluster Identity ‘%5′ has ‘Full Control’ permission to that computer object using the Active Directory Users and Computers tool.

1206
Microsoft-Windows-FailoverClustering Cluster network name resource ‘%1′ cannot be brought online. The computer object associated with the resource could not be updated in domain ‘%2′. The error code was ‘%3′. The cluster identity ‘%4′ may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain.
1207
Microsoft-Windows-FailoverClustering Cluster network name resource ‘%1′ cannot be brought online. The computer object associated with the resource could not be updated in domain ‘%2′ for the following reason:
%3.

The text for the associated error code is: %4

The cluster identity ‘%5′ may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain.

Failover Cluster Configuration Availability
Updated: November 25, 2009

The cluster configuration database contains essential information for the function of a failover cluster. A copy of the cluster configuration database is maintained on each node. If the quorum configuration for the cluster includes a witness disk, a copy of the cluster configuration database is also maintained on the witness disk. The Cluster service replicates the latest version of the cluster configuration database to all locations where it is stored.

Event ID

Source

Message

1057
Microsoft-Windows-FailoverClustering The cluster database could not be loaded. The file may be missing or corrupt. Automatic repair might be attempted.
1090
Microsoft-Windows-FailoverClustering The Cluster service cannot be started. An attempt to read configuration data from the Windows registry failed with error ‘%1′. Please use the Failover Cluster Management snap-in to ensure that this machine is a member of a cluster. If you intend to add this machine to an existing cluster use the Add Node Wizard. Alternatively, if this machine has been configured as a member of a cluster, it will be necessary to restore the missing configuration data that is necessary for the Cluster Service to identify that it is a member of a cluster. Perform a System State Restore of this machine in order to restore the configuration data.
1574
Microsoft-Windows-FailoverClustering The failover cluster database could not be unloaded. If restarting the cluster service does not fix the problem, please restart the machine.
1575
Microsoft-Windows-FailoverClustering An attempt to forcibly start the cluster service has failed because the cluster configuration data on this node is either missing or corrupt. Please first start the cluster service on another node that has an intact and valid copy of the cluster configuration data. Then, reattempt the start operation on this node (which will attempt to obtain updated valid configuration information automatically). If no other node is available, please use WBAdmin.msc to perform a System State Restore of this node in order to restore the configuration data.
1581
Microsoft-Windows-FailoverClustering The restore request for the cluster configuration data failed to make a copy of the existing cluster configuration data file (ClusDB). While attempting to preserve the existing configuration, the restore operation was unable to create a copy at location ‘%1′. This might be expected if the existing configuration data file was corrupt. The restore operation has continued but attempts to revert to the existing cluster configuration may not be possible.
1593
Microsoft-Windows-FailoverClustering The failover cluster database could not be unloaded and any potentially incorrect changes in memory could not be discarded. The cluster service will attempt to repair the database by retrieving it from another cluster node. If the cluster service does not come online, restart the cluster service on this node. If restarting the cluster service does not fix the problem, please restart the machine. If the cluster service fails to come online after a reboot, please restore the cluster database from the last backup. The current database was copied to ‘%1′. If no backups are available, please copy ‘%1′ to ‘%2′ and attempt to start the cluster service. If the cluster service then comes online on this node, some cluster configuration changes may be lost and the cluster may not function properly. Run the Validate a Configuration wizard to check your cluster configuration and verify that the hosted Services and Applications are online and functioning correctly.

Quorum and Connectivity Needed for Quorum
Updated: November 25, 2009

A failover cluster can run only when a majority of cluster elements (a quorum) are running and in communication. These elements usually include the nodes and, with some quorum configurations, a witness disk (which contains a copy of the cluster configuration) or witness file share. When enough of these elements are running and in communication, the cluster has achieved quorum and can run.

Event ID

Source

Message

1177
Microsoft-Windows-FailoverClustering The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk.
Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

Registry Checkpointing
Updated: November 25, 2009

Some clustered services and applications store information outside of the cluster configuration database, in registry keys that the Cluster service monitors and replicates between nodes. If the Cluster service is prevented from writing to such a registry key, the corresponding cluster resource might not function correctly.

Event ID

Source

Message

1024
Microsoft-Windows-FailoverClustering The registry checkpoint for cluster resource ‘%1′ could not be restored to registry key HKEY_LOCAL_MACHINE\%2. The resource may not function correctly. Make sure that no other processes have open handles to registry keys in this registry subtree.
1121
Microsoft-Windows-FailoverClustering Encrypted settings for cluster resource ‘%1′ could not be successfully applied to the container name ‘%2′ on this node.

Verbose Cluster Logging
Updated: November 25, 2009

You can turn on verbose cluster logging to provide additional detail in logs for troubleshooting. However, a failover cluster can function regardless of whether verbose cluster logging is turned on.

Event ID

Source

Message

1567
Microsoft-Windows-FailoverClustering Cluster service failed to change the trace log size. Please verify the ClusterLogSize setting with the ‘Get-Cluster | Format-List *’ PowerShell cmdlet. Also, use the Performance Monitor snapin to verify the event trace session settings for FailoverClustering.
4868
Microsoft-Windows-FailoverClustering Cluster service failed to start the cluster log trace session. The error code was ‘%2′. The cluster will function properly, but supplemental logging information will be missing. Use the Performance Monitor snapin to verify the event channel settings for ‘%1′.

Network Connectivity and Configuration
Updated: November 25, 2009

Each node in a failover cluster requires network connectivity with the other nodes. Problems with a network adapter or other network device (either physical problems or configuration problems) can interfere with connectivity.

Event ID

Source

Message

1096
Microsoft-Windows-FailoverClustering Cluster service cannot use network adapter %1 because it does not have a valid IP address assigned to it.
1289
Microsoft-Windows-FailoverClustering The Cluster Service was unable to access network adapter ‘%1′. Verify that other network adapters are functioning properly and check the device manager for errors associated with adapter ‘%1′. If the configuration for adapter ‘%1′ has been changed, it may become necessary to reinstall the failover clustering feature on this computer.
1290
Microsoft-Windows-FailoverClustering The Cluster Service was unable to determine the IPv6 address assigned to the %1 network adapter. Please be sure that IPv6 has not been disabled on the %1 network adapter.
1553
Microsoft-Windows-FailoverClustering This cluster node has no network connectivity. It cannot participate in the cluster until connectivity is restored. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
1554
Microsoft-Windows-FailoverClustering This cluster node has lost all network connectivity. It cannot participate in the cluster until connectivity is restored. The cluster service on this node will be terminated.
1572
Microsoft-Windows-FailoverClustering Node ‘%1′ failed to join the cluster because it could not send and receive failure detection network messages with other cluster nodes. Please run the Validate a Configuration wizard to ensure network settings. Also verify the Windows Firewall ‘Failover Clusters’ rules.
1583
Microsoft-Windows-FailoverClustering Cluster service failed to disable Internet Protocol security (IPsec) on the Failover cluster virtual adapter ‘%1′. This could have a negative impact on cluster communication performance. If this problem persists, please verify your local and domain connection security policies applying to IPSec and the Windows Firewall. Additionally, please check for events related to the Base Filtering Engine service.
4871
Microsoft-Windows-FailoverClustering The cluster service failed to start. This was because the failover cluster virtual adapter failed to initialize the miniport adapter. The error code was ‘%1′. Verify that other network adapters are functioning properly and check the device manager for errors. If the configuration was changed, it may be necessary to reinstall the failover clustering feature on this computer.
4872
Microsoft-Windows-FailoverClustering The failover cluster virtual adapter failed to generate a unique MAC address. Either it was unable to find a physical Ethernet adapter from which to generate a unique address or the generated address conflicts with another adapter on this machine. Please run the Validate a Configuration wizard to check your network configuration.

Backup and Restore Functionality in a Cluster
Updated: November 25, 2009

Successful backup and restore requires certain preconditions. The failover cluster must be running and must have quorum. Software used for backup and restore must be compatible with the Volume Shadow Copy Service (VSS) and with the VSS Writer used by failover clusters. For complete success in a restore, all nodes must be running throughout the time when the restore is performed. Also, the account used by the person performing the backup or restore must be an administrative account.

Event ID

Source

Message

1541
Microsoft-Windows-FailoverClustering The backup operation for the cluster configuration data has been aborted because quorum for the cluster has not yet been achieved. Please retry this backup operation after the cluster achieves quorum.
1542
Microsoft-Windows-FailoverClustering The restore request for the cluster configuration data has failed. This restore failed during the ‘pre-restore’ stage usually indicating that some nodes comprising the cluster are not currently operational. Ensure that the cluster service is running successfully on all nodes comprising this cluster.
1543
Microsoft-Windows-FailoverClustering The restore operation of the cluster configuration data has failed. This restore failed during the ‘post-restore’ stage usually indicating that some nodes comprising the cluster are not currently operational. It is recommended that you replace the current cluster configuration data file (ClusDB) with ‘%1′.
1544
Microsoft-Windows-FailoverClustering The backup operation for the cluster configuration data has been canceled. The cluster Volume Shadow Copy Service (VSS) writer received an abort request.
1545
Microsoft-Windows-FailoverClustering The restore operation for the cluster configuration data has failed. This was due to insufficient privileges associated with the user account performing the restore. Please ensure that the user account has local administrator privileges.
1582
Microsoft-Windows-FailoverClustering Cluster Service failed to move the restored cluster hive at ‘%1′ to ‘%2′. This may prevent the restore operation from succeeding successfully. If the cluster configuration was not properly restored, please retry the restore action.
4864
Microsoft-Windows-FailoverClustering Volume shadow copy service task resource ‘%1′ creation failed. The error code was ‘%2′.
4865
Microsoft-Windows-FailoverClustering Volume shadow copy service task resource ‘%1′ failed. The error code was ‘%2′. This is because the associated task could not be stopped as part of an offline operation. You may need to stop it manually using the Task Scheduler snapin.
4866
Microsoft-Windows-FailoverClustering Volume shadow copy service task resource ‘%1′ failed. The error code was ‘%2′. This is because the associated task could not be deleted as part of an offline operation. You may need to delete it manually using the Task Scheduler snapin.
4867
Microsoft-Windows-FailoverClustering Volume shadow copy service task resource ‘%1′ failed. The error code was ‘%2′. This is because the associated task could not be added as part of an online operation. Please use the Task Scheduler snapin to ensure your tasks are properly configured.

Cluster Service Startup
Updated: November 25, 2009

The Cluster service is the essential software component that controls all aspects of failover cluster operation and manages the cluster configuration database. If the Cluster service fails to start on a failover cluster node, the node cannot function as part of the cluster.

Event ID

Source

Message

1000
Microsoft-Windows-FailoverClustering Cluster service suffered an unexpected fatal error at line %1 of source module %2. The error code was %3.
1006
Microsoft-Windows-FailoverClustering Cluster service was halted due to incomplete connectivity with other cluster nodes.
1073
Microsoft-Windows-FailoverClustering The Cluster service was halted to prevent an inconsistency within the failover cluster. The error code was ‘%1′.
1105
Microsoft-Windows-FailoverClustering The Cluster service failed to start because it was unable to register interface(s) with the RPC service. The error code was ‘%1′.
1135
Microsoft-Windows-FailoverClustering Cluster node ‘%1′ was removed from the active failover cluster membership. The Cluster service on this node may have stopped. This could also be due to the node having lost communication with other active nodes in the failover cluster. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapters on this node. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
1146
Microsoft-Windows-FailoverClustering The cluster resource host subsystem (RHS) stopped unexpectedly. An attempt will be made to restart it. This is usually due to a problem in a resource DLL. Please determine which resource DLL is causing the issue and report the problem to the resource vendor.
1230
Microsoft-Windows-FailoverClustering Cluster resource ‘%1′ (resource type ‘%2′, DLL ‘%3′) either crashed or deadlocked. The Resource Hosting Subsystem (RHS) process will now attempt to terminate, and the resource will be marked to run in a separate monitor.
1234
Microsoft-Windows-FailoverClustering Cluster service has detected that its service account is missing one or more from the required set of privileges. The missing privilege list is: ‘%1′ and is not currently granted to the service account. Please use the ‘sc.exe qprivs clussvc’ to verify the privileges of the Cluster Service (ClusSvc). Additionally check for any security policies or group policies in the Active Directory that may have altered the default privileges. Type the following command to grant the Cluster Service the necessary privileges to function correctly:

sc.exe privs clussvc SeBackupPrivilege/SeRestorePrivilege/SeIncreaseQuotaPrivilege/SeIncreaseBasePriorityPrivilege/SeTcbPrivilege/SeDebugPrivilege/SeSecurityPrivilege/SeAuditPrivilege/SeImpersonatePrivilege/SeChangeNotifyPrivilege/SeIncreaseWorkingSetPrivilege/SeManageVolumePrivilege/SeCreateSymbolicLinkPrivilege

1247
Microsoft-Windows-FailoverClustering The Security Identifier (SID) type for the cluster service is configured as ‘%1′ but the expected SID type is ‘Unrestricted’. The cluster service is automatically modifying its SID type configuration with the Service Control Manager (SCM) and will restart in order for this change to take effect.
1248
Microsoft-Windows-FailoverClustering The Security Identifier (SID) ‘%1′ associated with the cluster service is not present in the process token. The cluster service will automatically correct this problem and restart.
1556
Microsoft-Windows-FailoverClustering The cluster service encountered an unexpected problem and will be shut down. The error code was ‘%2′.
1561
Microsoft-Windows-FailoverClustering The cluster service has determined that this node does not have the latest copy of cluster configuration data. Therefore, the cluster service has prevented itself from starting on this node.
Try starting the cluster service on all nodes in the cluster. If the cluster service can be started on other nodes with the latest copy of the cluster configuration data, this node will be able to subsequently join the started cluster successfully.

If there are no nodes available with the latest copy of the cluster configuration data, please consult the documentation for ‘Force Cluster Start’ in the failover cluster manager snapin, or the ‘forcequorum’ startup option. Note that this action of forcing quorum should be considered a last resort, since some cluster configuration changes may well be lost.

Node Cleanup Success
Updated: November 25, 2009

When a failover cluster is destroyed by running the Destroy Cluster command, the Cluster service requires access to disks in storage and other resources for complete removal of the cluster configuration. If this access is unavailable, you might need to take specific actions such as running a command to complete the removal of the configuration.

Event ID

Source

Message

4609
Microsoft-Windows-FailoverClustering Cluster service failed to retrieve the list of clustered disks while destroying the cluster. The error code was ‘%1′. If these disks are not accessible, execute the ‘Clear-ClusterDiskReservation’ PowerShell cmdlet.
4611
Microsoft-Windows-FailoverClustering Clustered disk with ID ‘%2′ was not released by the Partition Manager while destroying the cluster. The error code was ‘%1′. Restarting the machine will ensure the disk is released by the Partition Manager.
4613
Microsoft-Windows-FailoverClustering The cluster service failed to properly cleanup a clustered disk with ID ‘%2′ while destroying the cluster. The error code was ‘%1′. You may unable to access this disk until cleanup has been successfully completed. For manual cleanup, delete the ‘AttachedDisks’ value of the ‘HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ClusDisk\Parameters’ key in the Windows registry.
4615
Microsoft-Windows-FailoverClustering Disabling the cluster service during cluster node cleanup, has failed. The error code was ‘%1′. You may be unable to create or join a cluster with this machine until cleanup has been successfully completed. For manual cleanup, execute the ‘Clear-ClusterNode’ PowerShell cmdlet on this machine.
4616
Microsoft-Windows-FailoverClustering Termination of the cluster service during cluster node cleanup has not completed within the expected time period. Please restart this machine to ensure the cluster service is no longer running.
4618
Microsoft-Windows-FailoverClustering Resetting cluster service registry entries during cluster node cleanup failed. The error code was ‘%1′. You may be unable to create or join a cluster with this machine until cleanup has been successfully completed. For manual cleanup, execute the ‘Clear-ClusterNode’ PowerShell cmdlet on this machine.
4620
Microsoft-Windows-FailoverClustering Unloading the cluster service registry hive during cluster node cleanup failed. The error code was ‘%1′. You may be unable to create or join a cluster with this machine until cleanup has been successfully completed. For manual cleanup, execute the ‘Clear-ClusterNode’ PowerShell cmdlet on this machine.
4622
Microsoft-Windows-FailoverClustering Cluster node cleanup encounted at least one error. You may be unable to create or join a cluster with this machine until cleanup has been successfully completed. Please review and resolve preceding cluster node cleanup events. For manual cleanup, execute the ‘Clear-ClusterNode’ PowerShell cmdlet on this machine.
4624
Microsoft-Windows-FailoverClustering Resetting the IPSec security association timeout registry value failed during cluster node cleanup. The error code was ‘%1′. For manual cleanup, execute the ‘Clear-ClusterNode’ PowerShell cmdlet on this machine. Alternatively, you may reset the IPSec security association timeout by deleting the ‘%2′ value and the ‘%3′ value from HKEY_LOCAL_MACHINE in the Windows registry.
4625
Microsoft-Windows-FailoverClustering Resetting the IPSec security association timeout registry value failed during cluster node cleanup. This is because the IPSec security association timeout was modified after this machine was configured to be a member of a cluster. For manual cleanup, execute the ‘Clear-ClusterNode’ PowerShell cmdlet on this machine. Alternatively, you may reset the IPSec security association timeout by deleting the ‘%1′ value and the ‘%2′ value from HKEY_LOCAL_MACHINE in the Windows registry.

Node Membership in Cluster
Updated: November 25, 2009

Failover cluster nodes must have the ability to start the Cluster service, form a cluster (when a given node starts but no other nodes are up) and join a cluster (when a given node starts and discovers that one or more nodes are already up). This requires that certain conditions be met, for example, failover cluster nodes must run compatible versions of the operating system.

Event ID

Source

Message

1011
Microsoft-Windows-FailoverClustering Cluster node %1 has been evicted from the failover cluster.
1070
Microsoft-Windows-FailoverClustering The node failed to join failover cluster ‘%1′ due to error code ‘%2′.
1092
Microsoft-Windows-FailoverClustering Failed to form cluster ‘%1′ with error code ‘%2′. Failover cluster will not be available.
1093
Microsoft-Windows-FailoverClustering The Cluster service cannot identify node ‘%1′ as a member of failover cluster ‘%2′. If the computer name for this node was recently changed, consider reverting to the previous name. Alternatively, add the node to the failover cluster and if necessary, reinstall clustered applications.
1173
Microsoft-Windows-FailoverClustering Cluster service is shutting down because the membership engine detected a membership event while trying to join the server cluster. Shutting down is the normal response to this type of event. Cluster service will restart per the Service Manager’s recovery actions.
1282
Microsoft-Windows-FailoverClustering Security Handshake between Joiner and Sponsor did not complete in ‘%1′ Seconds, node terminating the connection
1283
Microsoft-Windows-FailoverClustering Sponsor node failed to Authorize the client request, Check whether the cluster service account at the Sponsor and the joiner nodes are the same
1546
Microsoft-Windows-FailoverClustering Node ‘%1′ failed to form a failover cluster. This was due to one or more nodes executing incompatible versions of the cluster service software. If node ‘%1′ or a different node in the cluster has been recently upgraded, please re-verify that all nodes are executing compatible versions of the cluster service software.
1547
Microsoft-Windows-FailoverClustering Node ‘%1′ attempted to join a failover cluster but failed due to incompatibility between versions of the cluster service software. If node ‘%1′ or a different node in the cluster has been recently upgraded, please verify that the changed cluster deployment with different versions of the cluster service software is supported.
1548
Microsoft-Windows-FailoverClustering Node ‘%1′ established a communication session with node ‘%2′ and detected that it is running a different but compatible version of the cluster service software. It is recommended that the same version of the cluster service software be installed on all nodes in the cluster.
1550
Microsoft-Windows-FailoverClustering Node ‘%1′ established a communication session with node ‘%2′ without performing a version compatibility check because version compatibility checking is disabled. Disabling version compatibility checking is not supported.
1551
Microsoft-Windows-FailoverClustering Node ‘%1′ formed a failover cluster without performing a version compatibility check because version compatibility checking is disabled. Disabling version compatibility checking is not supported.
1570
Microsoft-Windows-FailoverClustering Node ‘%1′ failed to establish a communication session while joining the cluster. This was due to an authentication failure. Please verify that the nodes are running compatible versions of the cluster service software.
1571
Microsoft-Windows-FailoverClustering Node ‘%1′ failed to establish a communication session while joining the cluster. This was due to an authorization failure. Please verify that the nodes are running compatible versions of the cluster service software.
4873
Microsoft-Windows-FailoverClustering The cluster service has detected that the failover cluster virtual adapter has stopped. This is expected when hot replace CPU is performed on this node. Cluster service will stop and should automatically restart after the operation is complete. Please check for additional events associated with the service and ensure that the cluster service has been restarted on this node.

Responsiveness of User-Mode Processes on Node
Updated: November 25, 2009

The Cluster service monitors the node to ensure that it does not remain in a state where essential processes are running (the kernel is running) but the node is unresponsive (user-mode processes cannot run). Unless the node is functioning both at the kernel level and the user-mode level, it cannot respond to client requests.

Event ID

Source

Message

4869
Microsoft-Windows-FailoverClustering User mode health monitoring has detected that the system is not being responsive. The Failover cluster virtual adapter has lost contact with the ‘%1′ process with a process ID ‘%2′, for ‘%3′ seconds. Please use Performance Monitor to evaluate the health of the system and determine which process may be negatively impacting the system.
4870
Microsoft-Windows-FailoverClustering User mode health monitoring has detected that the system is not being responsive. The Failover cluster virtual adapter has lost contact with the ‘%1′ process with a process ID ‘%2′, for ‘%3′ seconds. Recovery action will be taken.

Cluster Network Connectivity
Updated: November 25, 2009

A failover cluster requires network connectivity among nodes and between clients and nodes. Problems with a network adapter or other network device (either physical problems or configuration problems) can interfere with connectivity.

Event ID

Source

Message

1126
Microsoft-Windows-FailoverClustering Cluster network interface ‘%1′ for cluster node ‘%2′ on network ‘%3′ is unreachable by at least one other cluster node attached to the network. The failover cluster was not able to determine the location of the failure. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
1127
Microsoft-Windows-FailoverClustering Cluster network interface ‘%1′ for cluster node ‘%2′ on network ‘%3′ failed. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
1129
Microsoft-Windows-FailoverClustering Cluster network ‘%1′ is partitioned. Some attached failover cluster nodes cannot communicate with each other over the network. The failover cluster was not able to determine the location of the failure. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
1130
Microsoft-Windows-FailoverClustering Cluster network ‘%1′ is down. None of the available nodes can communicate using this network. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
1360
Microsoft-Windows-FailoverClustering Cluster IP address resource ‘%1′ failed to come online. Ensure the network property ‘%2′ matches a cluster network name or the address property ‘%3′ matches one of the subnets on a cluster network. If this is an IPv6 Address type, please verify that the cluster network matching this resource has at least one IPv6 prefix that is not link-local or tunnel.
1555
Microsoft-Windows-FailoverClustering Attempting to use IPv4 for ‘%1′ network adapter failed. This was due to a failure to disable IPv4 auto-configuration and DHCP. IPv6 will be used if enabled, else this node may not be able to participate in a failover cluster.
1569
Microsoft-Windows-FailoverClustering Network ‘%1′ which has been disabled for failover cluster use, was found to be the only currently possible network that node ‘%2′ can use to communicate with other nodes in the cluster. This may impact the node’s ability to participate in the cluster. Please verify network connectivity of node ‘%2′ and enable at least one network for cluster communication. Run the Validate a Configuration wizard to check your network configuration.
1592
Microsoft-Windows-FailoverClustering Cluster node ‘%1′ lost communication with cluster node ‘%2′. Network communication was reestablished. This could be due to communication temporarily being blocked by a firewall or connection security policy update. If the problem persists and network communication are not reestablished, the cluster service on one or more nodes will stop. If that happens, run the Validate a Configuration wizard to check your network configuration. Additionally, check for hardware or software errors related to the network adapters on this node, and check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

IP Address Resource Availability
Updated: November 25, 2009

In a cluster, an IP Address resource is important because in most cases, other resources (such as a Network Name resource) depend on it. An IP Address resource can come online only if it is configured correctly, and is supported correctly by available networks and network configurations.

Event ID

Source

Message

1044
Microsoft-Windows-FailoverClustering Encountered a failure when attempting to create a new NetBIOS interface while bringing resource ‘%1′ online (error code ‘%2′). The maximum number of NetBIOS names may have been exceeded.
1045
Microsoft-Windows-FailoverClustering No matching network interface found for resource ‘%1′ IP address ‘%2′ (return code was ‘%3′). If your cluster nodes span different subnets, this may be normal.
1046
Microsoft-Windows-FailoverClustering Cluster IP address resource ‘%1′ cannot be brought online because the subnet mask value is invalid. Please check your IP address resource properties.
1047
Microsoft-Windows-FailoverClustering Cluster IP address resource ‘%1′ cannot be brought online because the address value is invalid. Please check your IP address resource properties.
1048
Microsoft-Windows-FailoverClustering Cluster IP address resource ‘%1′ failed to come online. Configuration data for the network adapter corresponding to cluster network interface ‘%2′ could not be determined (error code was ‘%3′). Please check that the IP address resource is configured with the correct address and network properties.
1049
Microsoft-Windows-FailoverClustering Cluster IP address resource ‘%1′ cannot be brought online because a duplicate IP address ‘%2′ was detected on the network. Please ensure all IP addresses are unique.
1077
Microsoft-Windows-FailoverClustering Health check for IP interface ‘%1′ (address ‘%2′) failed (status is ‘%3′). Run the Validate a Configuration wizard to ensure that the network adapter is functioning properly.
1078
Microsoft-Windows-FailoverClustering Cluster IP address resource ‘%1′ cannot be brought online because WINS registration failed on interface ‘%2′ with error ‘%3′. Ensure that a valid, accessible WINS server has been specified.
1223
Microsoft-Windows-FailoverClustering Cluster IP address resource ‘%1′ cannot be brought online because the cluster network ‘%2′ is not configured to allow client access. Please use the Failover Cluster Manager snap-in to check the configured properties of the cluster network.
1240
Microsoft-Windows-FailoverClustering Cluster IP address resource ‘%1′ failed to obtain a leased IP address.
1242
Microsoft-Windows-FailoverClustering Lease of IP address ‘%2′ associated with cluster IP address resource ‘%1′ has expired or is about to expire, and currently cannot be renewed. Ensure that the associated DHCP server is accessible and properly configured to renew the lease on this IP address.
1243
Microsoft-Windows-FailoverClustering Cluster IP address resource ‘%1′ failed to release the lease for IP address ‘%2′.
1245
Microsoft-Windows-FailoverClustering Cluster IP address resource ‘%1′ failed to renew the lease for IP address ‘%2′. Ensure that the DHCP server is accessible and properly configured to renew the lease on this IP address.
1361
Microsoft-Windows-FailoverClustering IPv6 Tunnel address resource ‘%1′ failed to come online because it does not depend on an IP Address (IPv4) resource. Dependency on at least one IP Address (IPv4) resource is required.
1362
Microsoft-Windows-FailoverClustering Cluster IP address resource ‘%1′ failed to come online because the ‘%2′ property could not be read. Please ensure that the resource is correctly configured.
1363
Microsoft-Windows-FailoverClustering IPv6 tunnel address resource ‘%1′ failed to come online. Cluster network ‘%2′ associated with dependent IP address (IPv4) resource ‘%3′ does not support ISATAP tunneling. Please ensure that the cluster network supports ISATAP tunneling.

Network Name Resource Availability
Updated: November 25, 2009

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.

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.

File Share Resource Availability
Updated: November 25, 2009

Clients can access folders and files on a clustered file server only when the corresponding file share resource is available.

Event ID

Source

Message

1053
Microsoft-Windows-FailoverClustering Cluster File Share ‘%1′ cannot be brought online because the share could not be created.
1054
Microsoft-Windows-FailoverClustering Health check for file share resource ‘%1′ failed. Retrieving information for share ‘%2′ (scoped to network name %3) returned error code ‘%4′. Ensure the share exists and is accessible.
1055
Microsoft-Windows-FailoverClustering Health check for file share resource ‘%1′ failed. Retrieving information for share ‘%2′ (scoped to network name %3) indicated that the share does not exist (error code ‘%4′). Please ensure the share exists and is accessible.
1068
Microsoft-Windows-FailoverClustering Cluster file share resource ‘%1′ cannot be brought online. Creation of file share ‘%2′ (scoped to network name %3) failed due to error ‘%4′. This operation will be automatically retried.
1560
Microsoft-Windows-FailoverClustering Cluster file share resource ‘%1′ has detected shared folder conflicts. As a result, some of these shared folders may not be accessible. To rectify this situation, ensure multiple shared folders do not have the same share name.
1585
Microsoft-Windows-FailoverClustering Cluster file server resource ‘%1′ failed a health check. This was due to the Server service not being started. Please use Server Manager to confirm the state of the Server service on this cluster node.
1586
Microsoft-Windows-FailoverClustering Cluster file server resource ‘%1′ failed a health check. This was because some of its shared folders were inaccessible. Verify that the folders are accessible from clients. Additionally, confirm the state of the Server service on this cluster node using Server Manager and look for other events related to the Server service on this cluster node. It may be necessary to restart the network name resource ‘%2′ in this clustered service or application.
1587
Microsoft-Windows-FailoverClustering Cluster file server resource ‘%1′ failed a health check. This was because some of its shared folders were inaccessible. Verify that the folders are accessible from clients. Additionally, confirm the state of the Server service on this cluster node using Server Manager and look for other events related to the Server service on this cluster node.
1588
Microsoft-Windows-FailoverClustering Cluster file server resource ‘%1′ cannot be brought online. The resource failed to create file share ‘%2′ associated with network name ‘%3′. The error code was ‘%4′. Verify that the folders exist and are accessible. Additionally, confirm the state of the Server service on this cluster node using Server Manager and look for other related events on this cluster node. It may be necessary to restart the network name resource ‘%3′ in this clustered service or application.

DHCP or WINS Resource Availability
Updated: November 25, 2009

For a clustered Dynamic Host Configuration Protocol (DHCP) server to function, the clustered DHCP resource must be online. Similarly, for a clustered Windows Internet Name Service (WINS) server to function, the clustered WINS resource must be online.

Event ID

Source

Message

1181
Microsoft-Windows-FailoverClustering Cluster resource ‘%1′ cannot be brought online because the associated service failed to start. The service return code is ‘%2′. Please check for additional events associated with the service and ensure the service starts correctly.
1182
Microsoft-Windows-FailoverClustering Cluster resource ‘%1′ cannot be brought online because the associated service failed an attempted restart. The error code is ‘%2′. The service required a restart in order to update parameters. However, the service failed before it could be stopped and restarted. Please check for additional events associated with the service and ensure the service is functioning correctly.

DFS Namespace Resource Availability
Updated: November 25, 2009

A clustered DFS Namespace requires a clustered disk resource containing a shared folder or folders. If these resources are not online, the clustered DFS Namespace cannot function.

Event ID

Source

Message

1138
Microsoft-Windows-FailoverClustering Cluster file share resource ‘%1′ cannot be brought online. Creation of DFS namespace root failed with error ‘%3′. This may be due to failure to start the ‘DFS Namespace’ service or failure to create the DFS-N root for share ‘%2′.
1141
Microsoft-Windows-FailoverClustering Cluster file share resource ‘%1′ cannot be brought online. Resynchronization of DFS root target ‘%2′ failed with error ‘%3′.
1142
Microsoft-Windows-FailoverClustering Cluster file share resource ‘%1′ for DFS Namespace cannot be brought online due to error ‘%2′.

Generic Script Resource Availability
Updated: November 25, 2009

For a clustered Generic Script instance, the correct functioning of the script is very important in determining whether the combination of Cluster service, script, and application will work together to increase availability.

Event ID

Source

Message

1232
Microsoft-Windows-FailoverClustering Entry point ‘%2′ in cluster generic script resource ‘%1′ did not complete execution in a timely manner. This could be due to an infinite loop or other issues possibly resulting in an infinite wait. Alternatively, the specified pending timeout value may be too short for this resource. Please review the ‘%2′ script entry point to ensure all possible infinite waits in the script code have been corrected. Then, consider increasing the pending timeout value if deemed necessary.
1233
Microsoft-Windows-FailoverClustering Cluster generic script resource ‘%1′: request to perform the ‘%2′ operation will not be processed. This is due to a previously failed attempt to execute the ‘%3′ entry point in a timely fashion. Please review the script code for this entry point to ensure there does not exist any infinite loop or other issues possibly resulting in an infinite wait. Then, consider increasing the resource pending timeout value if deemed necessary.

Generic Service Resource Availability
Updated: November 25, 2009

The service used by a clustered Generic Service instance must start and run correctly before clients can use it. If any settings related to the service or the associated clustered resource are incorrect, the clustered Generic Service instance cannot function correctly.

Event ID

Source

Message

1040
Microsoft-Windows-FailoverClustering Generic service ‘%1′ could not be brought online (with error ‘%2′) during an attempt to open the service. Possible causes include: the service is either not installed or the specified service name is invalid.
1041
Microsoft-Windows-FailoverClustering Generic service ‘%1′ could not be brought online (with error ‘%2′) during an attempt to start the service. Possible cause: the specified service parameters might be invalid.
1042
Microsoft-Windows-FailoverClustering Generic service ‘%1′ failed with error ‘%2′. Please examine the application event log.

Generic Application Resource Availability
Updated: November 25, 2009

This aspect provides information to help you interpret system messages that indicate whether the Generic Application resource is operational.

Event ID

Source

Message

1039
Microsoft-Windows-FailoverClustering Generic application ‘%1′ could not be brought online (with error ‘%2′) during an attempt to create the process. Possible causes include: the application may not be present on this node, the path name may have been specified incorrectly, the binary name may have been specified incorrectly.

Clustered Service or Application Availability
Updated: November 25, 2009

In a failover cluster, a clustered service or application can come online (and be available for clients to use) only when the necessary clustered resources within it can come online.

Event ID

Source

Message

1069
Microsoft-Windows-FailoverClustering Cluster resource ‘%1′ in clustered service or application ‘%2′ failed.
1205
Microsoft-Windows-FailoverClustering The Cluster service failed to bring clustered service or application ‘%1′ completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.

Cluster Witness Functionality
Updated: November 25, 2009

In a cluster with an even number of nodes and a quorum configuration that includes a witness, when the witness remains online, the cluster can sustain failures of half the nodes. If the witness goes offline, the same cluster can sustain failures of half the nodes minus one.

Event ID

Source

Message

1557
Microsoft-Windows-FailoverClustering Cluster service failed to update the cluster configuration data on the witness resource. Please ensure that the witness resource is online and accessible.
1558
Microsoft-Windows-FailoverClustering The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data.
1559
Microsoft-Windows-FailoverClustering File share ‘%1′ associated with the file share witness resource is currently hosted by server ‘%2′. This server ‘%2′ has just been added as a new node within the failover cluster. Hosting of the file share witness by any node comprising the same cluster is not recommended. Please choose a file share witness that is not hosted by any node within the same cluster and modify settings of the file share witness resource accordingly.
1562
Microsoft-Windows-FailoverClustering File share witness resource ‘%1′ failed a periodic health check on file share ‘%2′. Please ensure that file share ‘%2′ exists and is accessible by the cluster.
1563
Microsoft-Windows-FailoverClustering File share witness resource ‘%1′ failed to come online. Please ensure that file share ‘%2′ exists and is accessible by the cluster.
1564
Microsoft-Windows-FailoverClustering File share witness resource ‘%1′ failed to arbitrate for the file share ‘%2′. Please ensure that file share ‘%2′ exists and is accessible by the cluster.
1573
Microsoft-Windows-FailoverClustering Node ‘%1′ failed to form a cluster. This was because the witness was not accessible. Please ensure that the witness resource is online and available.

Cluster Shared Volume Backup
Updated: November 25, 2009

Because of the design of Cluster Shared Volumes, backup applications for these volumes must meet specific requirements for compatibility. The Cluster Shared Volumes feature allows volumes in cluster storage to be accessed by all nodes of a failover cluster. This makes it possible for virtual machines to use volumes on the same LUN (disk) while still being able to fail over (or move from node to node) independently of one another.

Event ID

Source

Message

1584
Microsoft-Windows-FailoverClustering A backup application initiated a VSS snapshot on Cluster Shared Volume ‘%1′ (‘%3′) without properly preparing the volume for snapshot. This snapshot may be invalid and the backup may not be usable for restore operations. Please contact your backup application vendor to verify compatibility with Cluster Shared Volumes.

Cluster Shared Volume Functionality
Updated: November 25, 2009

In a failover cluster, virtual machines can use Cluster Shared Volumes that are on the same LUN (disk), while still being able to fail over (or move from node to node) independently of one another. Virtual machines can use a Cluster Shared Volume only when communication between the cluster nodes and the volume is functioning correctly, including network connectivity, access, drivers, and other factors.

Event ID

Source

Message

5120
Microsoft-Windows-FailoverClustering Cluster Shared Volume ‘%1′ (‘%2′) is no longer available on this node because of ‘%3′. All I/O will temporarily be queued until a path to the volume is reestablished.
5121
Microsoft-Windows-FailoverClustering Cluster Shared Volume ‘%1′ (‘%2′) is no longer directly accessible from this cluster node. I/O access will be redirected to the storage device over the network through the node that owns the volume. This may result in degraded performance. If redirected access is turned on for this volume, please turn it off. If redirected access is turned off, please troubleshoot this node’s connectivity to the storage device and I/O will resume to a healthy state once connectivity to the storage device is reestablished.
5123
Microsoft-Windows-FailoverClustering Cluster service failed to create the Cluster Shared Volumes root directory ‘%2′. The error message was ‘%1′.
5124
Microsoft-Windows-FailoverClustering Cluster Shared Volumes root directory ‘%1′ already exists. The directory ‘%1′ was renamed to ‘%2′. Please verify that applications accessing data in this location have been updated as necessary.
5125
Microsoft-Windows-FailoverClustering Cluster Shared Volume ‘%1′ (‘%3′) has identified one or more active filter drivers on this device stack that could interfere with CSV operations. I/O access will be redirected to the storage device over the network through another Cluster node. This may result in degraded performance. Please contact the filter driver vendor to verify interoperability with Cluster Shared Volumes.

Active filter drivers found:
%2

5126
Microsoft-Windows-FailoverClustering Cluster Shared Volume ‘%1′ (‘%3′) has identified one or more active volume drivers on this device stack that could interfere with CSV operations. I/O access will be redirected to the storage device over the network through another Cluster node. This may result in degraded performance. Please contact the volume driver vendor to verify interoperability with Cluster Shared Volumes.

Active volume drivers found:
%2

5128
Microsoft-Windows-FailoverClustering Physical disk resource ‘%1′ does not allow disabling short name generation. This may cause application compatibility issues. Please use ‘fsutil 8dot3name set 2′ to allow disabling short name generation and then offline/online the resource.
5133
Microsoft-Windows-FailoverClustering Cluster Disk ‘%1′ has been removed and placed back in the ‘Available Storage’ cluster group. During this process an attempt to restore the original drive letter(s) has taken longer than expected, possibly due to those drive letters being already in use.
5134
Microsoft-Windows-FailoverClustering Cluster service failed to set the permissions (ACL) on the Cluster Shared Volumes root directory ‘%1′. The error was ‘%2′.
5135
Microsoft-Windows-FailoverClustering Cluster service failed to set the permissions on the Cluster Shared Volume directory ‘%1′ (‘%2′). The error was ‘%3′.
5136
Microsoft-Windows-FailoverClustering Cluster Shared Volume ‘%1′ (‘%2′) redirected access was turned on. Access to the storage device will be redirected over the network from all cluster nodes that are accessing this volume. This may result in degraded performance. Please turn off redirected access for this volume.
5142
Microsoft-Windows-FailoverClustering Cluster Shared Volume ‘%1′ (‘%2′) is no longer accessible from this cluster node because of error ‘%3′. Please troubleshoot this node’s connectivity to the storage device and network connectivity.
5200
Microsoft-Windows-FailoverClustering Cluster service failed to create a cluster identity token for Cluster Shared Volumes. The error code was ‘%1′. Ensure the domain controller is accessible and check for connectivity issues. Until connection to the domain controller is recovered, some operations on this node against the Cluster Shared Volumes might fail.

Cluster Storage Functionality
Updated: November 25, 2009

In a failover cluster, most clustered services or applications use at least one disk, also called a disk resource, that you assign when you configure the clustered service or application. Clients can use the clustered service or application only when the disk is functioning correctly.

Event ID

Source

Message

1034
Microsoft-Windows-FailoverClustering Cluster physical disk resource ‘%1′ cannot be brought online because the associated disk could not be found. The expected signature of the disk was ‘%2′. If the disk was replaced or restored, in the Failover Cluster Manager snap-in, you can use the Repair function (in the properties sheet for the disk) to repair the new or restored disk. If the disk will not be replaced, delete the associated disk resource.
1035
Microsoft-Windows-FailoverClustering While disk resource ‘%1′ was being brought online, access to one or more volumes failed with error ‘%2′. Run the Validate a Configuration wizard to check your storage configuration. Optionally you may want to run Chkdsk to verify the integrity of all volumes on this disk.
1037
Microsoft-Windows-FailoverClustering The file system for one or more partitions on the disk for resource ‘%1′ may be corrupt. Run the Validate a Configuration wizard to check your storage configuration. Optionally, you may want to run Chkdsk to verify the integrity of all volumes on this disk.
1038
Microsoft-Windows-FailoverClustering Ownership of cluster disk ‘%1′ has been unexpectedly lost by this node. Run the Validate a Configuration wizard to check your storage configuration.
1066
Microsoft-Windows-FailoverClustering Cluster disk resource ‘%1′ indicates corruption for volume ‘%2′. Chkdsk is being run to repair problems. The disk will be unavailable until Chkdsk completes. Chkdsk output will be logged to file ‘%3′.
Chkdsk may also write information to the Application Event Log.
1080
Microsoft-Windows-FailoverClustering The Cluster service failed to update the cluster database (error code ‘%1′). Possible causes are insufficient disk space or file system corruption.
1183
Microsoft-Windows-FailoverClustering Cluster disk resource ‘%1′ contains an invalid mount point. Both the source and target disks associated with the mount point must be clustered disks, and must be members of the same group.
Mount point ‘%2′ for volume ‘%3′ references an invalid source disk. Please ensure that the source disk is also a clustered disk and in the same group as the target disk (hosting the mount point).
1208
Microsoft-Windows-FailoverClustering Cluster disk resource ‘%1′ contains an invalid mount point. Both the source and target disks associated with the mount point must be clustered disks, and must be members of the same group.
Mount point ‘%2′ for volume ‘%3′ references an invalid target disk. Please ensure that the target disk is also a clustered disk and in the same group as the source disk (hosting the mount point).
1568
Microsoft-Windows-FailoverClustering Cluster disk resource ‘%1′ found the disk identifier to be stale. This may be expected if a restore operation was just performed or if this cluster uses replicated storage. The DiskSignature or DiskUniqueIds property for the disk resource has been corrected.
Share and Enjoy:
  • Print
  • Digg
  • Facebook
  • Google Bookmarks
  • email
  • Live
  • MySpace
  • PDF
  • RSS
  • Twitter

Leave a Reply

(required)

(required)