Cluster service encountered a fatal error. The vital quorum log file '%1' is corrupt. If you have a backup of the quorum log file, you may try to start Cluster service with logging disabled by entering net start clussvc /noquorumlogging at a command window, copy the backed up quorum log file to the MSCS directory on the quorum drive, stop Cluster service using 'net stop clussvc', and restart Cluster service with logging re-enabled using the 'net start clussvc' command. If you do not have a backup of the quorum log file, you may try to start Cluster service by entering net start clussvc /resetquorumlog at a command window. This will attempt to create a new quorum log file based on possibly stale information in the server cluster database. You may then stop Cluster service and restart it with logging re-enabled using the 'net start clussvc' command.
Cluster service did not start because the current version of Windows is not correct. Cluster service runs only on Windows ...
Cluster service discovered that the node is attached to a new network by adapter %1. A new network and a network interface ...
Cluster service discovered that the node is now attached to cluster network '%1' by adapter %2. A new cluster network interface ...
Cluster service encountered a fatal error. The vital quorum log file '%1' could not be found. If you have a backup of the ...
Cluster service encountered a fatal error. The vital quorum log file '%1' is corrupt. If you have a backup of the quorum ...
Cluster service failed to access the Cluster Network driver. The error code was %1. Please check Cluster service installation. ...
Cluster service failed to delete an unused network interface from the server cluster configuration. The error code was %1. ...
Cluster service failed to initialize due to an invalid file specification in the CLUSTERLOG environment variable. Please ...
Cluster service failed to initialize the Windows Sockets interface. The error code was %1. Please check the network configuration ...