| Previous | Next |
| ERROR_DEPENDENCY_NOT_ALLOWED | ERROR_NODE_CANT_HOST_RESOURCE |
ERROR_CLUSTER_NODE_PAUSED
A paused node remains a cluster member but is normally excluded from receiving new roles. This can be an intentional maintenance state or an operational state that needs to be understood before resuming it.
Confirm whether the pause and drain were intentional and whether roles remain on the node. Resume only after maintenance prerequisites are satisfied; unexpected pause state should be traced back to the management action that set it.
What to check
- Confirm whether the pause was planned and whether roles were drained or moved elsewhere.
- Check the current owner and state of clustered groups before resuming the node.
- If the node paused unexpectedly, inspect the cluster log for the preceding action or health event.
Get-ClusterNode; Get-ClusterGroupLooking for a different code? Search another status or error code.