Cluster Service Startup
Applies To: Windows Server 2008 R2
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.
Events
| Event ID | Source | Message |
|---|---|---|
Microsoft-Windows-FailoverClustering |
Cluster service suffered an unexpected fatal error at line %1 of source module %2. The error code was %3. | |
Microsoft-Windows-FailoverClustering |
Cluster service was halted due to incomplete connectivity with other cluster nodes. | |
Microsoft-Windows-FailoverClustering |
The Cluster service was halted to prevent an inconsistency within the failover cluster. The error code was '%1'. | |
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'. | |
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. | |
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. | |
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. | |
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 |
|
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. | |
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. | |
Microsoft-Windows-FailoverClustering |
The cluster service encountered an unexpected problem and will be shut down. The error code was '%2'. | |
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. |