| Previous | Next |
| ERROR_NONCORE_GROUPS_FOUND | ERROR_CLUSTER_EVICT_INVALID_REQUEST |
ERROR_FILE_SHARE_RESOURCE_CONFLICT
A file share witness must remain independent of the cluster it votes for
ERROR_FILE_SHARE_RESOURCE_CONFLICT means the selected share for a file share witness is hosted by the cluster being configured or by one of its member nodes. A witness must provide an independent vote during failures. Hosting it on the same failure domain creates a circular dependency: loss of the cluster or node also removes the vote needed to decide cluster membership.
Place the witness on a separate server or supported non-domain device with reliable SMB access from all nodes. Use a dedicated share, grant the cluster identity the required permissions, and avoid DFS or replicated storage for the witness path. Confirm DNS, authentication, and firewall access from every node before changing quorum.
Witness independence checks
- Share server is not a cluster node or a clustered file-server role in the same cluster.
- The witness resides in an independent failure domain.
- All nodes can authenticate to the same UNC path.
- The share is dedicated and not implemented through unsupported DFS replication.
References
- Microsoft: configuring a file share witness
- Microsoft: supported witness placement and share requirements
- Microsoft: why the witness participates in quorum
Looking for a different code? Search another status or error code.