Clustered role '%1' has exceeded its failover threshold. It has exhausted the configured number of failover 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 role online or fail it over to another node in the cluster. Please check the events associated with the failure. After the issues causing the failure are resolved the role can be brought online manually or the cluster may attempt to bring it online again after the restart delay period.
Cluster-Aware Updating may not be able to update this failover cluster. An Updating Run that applies updates that require ...
Clustered disk with ID '%2' was not released by the Partition Manager while destroying the cluster. The error code was '%1'. ...
Clustered disks can be added to Cluster Shared Volumes or assigned exclusively to clustered roles. Navigate to Disks to add, ...
Clustered disks have been released by the Partition Manager while destroying the cluster. These disks will be left in an ...
Clustered role '%1' has exceeded its failover threshold. It has exhausted the configured number of failover attempts within ...
Clustered role '%2' was taken offline. This role was preempted by the higher priority clustered role '%1'. The cluster service ...
Clustered service or application '%1' has exceeded its failover threshold. It has exhausted the configured number of failover ...
Clustered storage pools are groups of physical disks that are logically combined and managed as one or more virtual disks ...
Clustering Services have been detected on this node. Certain clustering functionality may be impaired by Internet Connection ...