| Previous | Next |
| ERROR_NODE_NOT_AVAILABLE | ERROR_RESOURCE_FAILED |
ERROR_ALL_NODES_NOT_AVAILABLE
A cluster-wide operation requires full node participation
Some cluster changes require a consistent view or action across all nodes rather than quorum alone. A cluster can continue serving workloads with a node down and still reject an administrative operation that explicitly requires every node to be available.
Do not confuse service availability with operation eligibility. Quorum can be healthy while a cluster-wide configuration task waits for a missing node. Identify the unavailable node and the operation being attempted before changing quorum or failing over roles.
What to inspect
- List all nodes and find any Down, Paused, or otherwise unavailable members.
- Determine whether the node is intentionally under maintenance; finish or reverse that workflow before retrying the cluster-wide change.
- If a node is permanently lost, follow supported node removal or recovery procedures instead of repeatedly retrying an operation that requires it.
Get-ClusterNode | Format-Table Name, StateReferences
- Microsoft: FailoverClusters PowerShell module
- Microsoft Open Specifications: MS-CMRP glossary
- Microsoft: Get-ClusterLog
Looking for a different code? Search another status or error code.