Cluster resource '%1' in clustered role '%2' has exceeded the maximum number of consecutive failures. It has exhausted the number of restart attempts within the failover period of time allotted to it and will be left in a failed state. No additional attempts will be made to bring the resource online. Check the events associated with the failure. After the issues causing the failure are resolved the resource can be brought online manually or the cluster may attempt to bring it online again after the restart delay period.
Cluster physical disk resource '%1' cannot be brought online because the associated disk could not be found. The expected ...
Cluster physical disk resource '%1' failed. The Cluster Shared Volume was put in failed state with the following error: '%2' ...
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 exceeded the maximum number of consecutive failures. It has exhausted the ...
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' has received a critical state notification. For a virtual machine this indicates ...
Cluster resource '%1' in clustered role '%2' has taken more than one minute to respond to a control code. The control code ...
Cluster resource '%1' in clustered role '%2' has transitioned from state %3 to state %4. Cluster resource '%1' is waiting ...