| Event Id | 1147 |
| Source | ClusSvc |
| Description | The Microsoft Clustering Service encountered a fatal error. The vital quorum log file Q:\MSCS\quolog.log could not be found. If you have a backup of the quorum log file, you may try to start the cluster service by entering clussvc -debug -noquorumlogging at a command window, copy the backed up quorum log file to the MSCS directory in the quorum drive, stop the cluster service, and restart the cluster service normally using the net start clussvc command. If you do not have a backup of the quorum log file, you may try to start the cluster service as clussvc -debug -resetquorumlog and this will attempt to create a new quorum log file based on possibly stale information in the cluster hive. You may then stop the cluster service and restart it normally using the net start clussvc command. |
| Event Information | According to Microsoft: CAUSE: This error message occurs if the quorum log file (Quolog.log) cannot be found or read at Cluster service startup. It must be readable to confirm that the cluster configuration on the local node is up-to-date. If it cannot read the log, the Cluster service does not start to prevent potentially loading stale configuration data. RESOLUTION: If you do not have a backup of the Quorum log file, re-create a new quorum log file based on the cluster configuration information in the local systems cluster hive by starting the Cluster service with the -ResetQuorumLog switch. To do this, follow these steps: 1. Start the Services snap-in. (Click Start, point to Programs, click Administrative Tools, and then click Services.) 2. Right-click and select the properties of the Cluster service. 3. In the Start Parameters box, type: -resetquorumlog Then click the Start button. |
| Reference Links | Recovering from a lost or corrupted quorum log |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.