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.
Majority Node Set resource has failed a status check for file share"\\abcdef\clustername". The error code was "53". Please ensure that the file share is configured properly and that the cluster service account has write permission on the file share.
|English: Request a translation of the event description in plain English.|
In my case, the event description mentioned Error code 53. This event could be fixed very simply via command line and Cluster command. The root cause is that arbitrator of cluster clx is not configured properly in my case it was due to decommissioning of 3rd ( arbitrator server) and the cluster configuration was not changed to the new server.
(CLX are using arbitrators like 3rd nodes - but it is simply share on 3rd server in 3rd, separate datacenter).
You can use these commands to fix the problem:
- cluster res / priv
- cluster res MNS (could be another resource name ) / priv resource name=server name where is share/directory prepared
|Private comment: Subscribers only. See example of private comment|
|Links: Error code 53, Error code 1326|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated