Cluster resource '%1' failed to go online because its associated computer account (%2) exists in Active Directory and the Kerberos authentication is not enabled for the resource. Client applications that are using Kerberos based authentication (either directly or through the Negotiate security package) will fail to authenticate when contacting a service by this network name. To bring the resource online, either enable Kerberos authentication or delete the computer account.
Cluster node %1 failed a critical operation. It will be removed from the active server cluster membership. Check that the ...
Cluster node %1 was not able to obtain a multicast address from a MADCAP server for network %2 or to select one automatically. ...
Cluster node %1 was removed from the active server cluster membership. Cluster service may have been stopped on the node, ...
Cluster resource %1 timed out. If the pending timeout is too short for this resource, consider increasing the pending timeout ...
Cluster resource '%1' failed to go online because its associated computer account (%2) exists in Active Directory and the ...
Cluster resource monitor detected a deadlock possibly caused by invoking the '%4' entry point of resource DLL '%1', resource ...
Cluster service could not join an existing server cluster and could not form a new server cluster. Cluster service has terminated. ...
Cluster service could not write to a file (%1). The disk may be low on disk space, or some other serious condition exists. ...
Cluster service did not find any network adapters with valid IP addresses installed in the system. The node will not be able ...