| Previous | Next |
| ERROR_CLUSTER_NO_NET_ADAPTERS | ERROR_CLUSTER_GROUP_MOVING |
ERROR_CLUSTER_POISONED
ERROR_CLUSTER_POISONED indicates that the cluster marked a node or operation as unreliable after a serious failure. Treat it as a symptom requiring evidence collection, not as a state to override by force.
Preserve the events and Cluster.log around the failure that caused the poison state before restarting or clearing anything. The protective marker is less important than the underlying crash, timeout, or repeated resource failure that triggered it.
What to check
- Collect cluster and System logs before restarting or rejoining the affected node.
- Look for repeated resource host crashes, storage failures, or membership transitions immediately before the poison event.
- Validate the node only after the underlying hardware, network, or resource-DLL issue is resolved.
Get-ClusterLog -UseLocalTime -Destination C:\TempLooking for a different code? Search another status or error code.