Cluster resource '%1' (resource type '%2', DLL '%3') did not respond to a request in a timely fashion. Cluster health detection will attempt to automatically recover by terminating the Resource Hosting Subsystem (RHS) process running this resource. This may affect other resources hosted in the same RHS process. The resources will then be restarted. The suspect resource '%1' will be marked to run in an isolated RHS process to avoid impacting multiple resources in the event that this resource failure occurs again. Please ensure services, applications, or underlying infrastructure (such as storage or networking) associated with the suspect resource is functioning properly.
Cluster network name resource '%1' was unable to identify any IP addresses to register with a DNS server. Ensure that there ...
Cluster node '%1' lost communication with cluster node '%2'. Network communication was reestablished. This could be due to ...
Cluster node '%1' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. ...
Cluster physical disk resource '%1' cannot be brought online because the associated disk could not be found. The expected ...
Cluster resource '%1' (resource type '%2', DLL '%3') did not respond to a request in a timely fashion. Cluster health detection ...
Cluster resource '%1' cannot be brought online because the associated service failed an attempted restart. The error code ...
Cluster resource '%1' cannot be brought online because the associated service failed to start. The service return code is ...
Cluster resource '%1' in clustered role '%2' has received a critical state notification. For a virtual machine this indicates ...
Cluster resource '%1' in clustered role '%2' rejected a move request to node '%3'. The error code was '%4'. Cluster resource ...