Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
The log file Q:\MSCS\quolog.log was found to be corrupt. An attempt will be made to reset it, or you should use the Cluster Administrator utility to adjust the maximum size.
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
Where can I find Cluster Administrator console?
What is the role of the Cluster Service?
See ME225081 for information on how to change the quorum log size of a cluster.
See ME172951 and ME872970 for details on fixing this problem.
The error message can occur if the quorum log file (Quolog.log) cannot be found or read at Cluster service startup. This file must be readable to confirm that the cluster configuration on the local node is current. If the Cluster service cannot read the log, the service is not prevented from loading stale configuration data. The log file may be corrupted if the time and date stamp of the Chk xxx .tmp file does not match the stamp of the Quolog.log file in the \MSCS folder on the quorum drive. The corruption can occur if you recently performed a restore operation, or if you experienced a power outage. See ME257905 for resolution.
|Private comment: Subscribers only. See example of private comment|
|Links: ME172951, ME225081, ME257905, ME872970|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated