ERROR_CANT_EVICT_ACTIVE_NODE - 5009 (0x1391)
A cluster node cannot be evicted from the cluster unless the node is down or it is the last node.
Updated: Feb 21, 2026
Technical Background
ERROR_CANT_EVICT_ACTIVE_NODE, with the numeric code 5009 and hex code 0x1391, is a specific error encountered in Windows cluster environments. This error indicates that an attempt to evict a node from a cluster has failed because the node is active, meaning it is currently participating in the cluster operations.
Error Details
The error message states that a cluster node cannot be evicted unless the node is down or if it is the last node remaining in the cluster. This restriction ensures the integrity and stability of the cluster by preventing the removal of nodes that are still active, which could disrupt ongoing services and operations.
Common Causes
- Active Node: The node being attempted to be evicted is currently performing critical functions within the cluster and cannot be safely removed without causing service disruptions.
- Last Node in Cluster: If there is only one node left in the cluster, it cannot be evicted as this would leave the cluster in an unusable state.
Real-World Context
In a Windows Failover Cluster, nodes are typically used to host resources and services. Evicting a node from such a cluster involves stopping all services on that node and removing it from the cluster membership. This process is carefully managed to ensure no service interruptions occur during the transition.
Is This Error Critical?
Yes, this error indicates a critical state in the cluster where an operation cannot proceed as intended without resolving the underlying issue. It should be addressed promptly to maintain the stability and availability of the cluster services.
How to Diagnose
- Review Operation Context: Ensure that the node being evicted is not currently active or hosting any critical resources.
- Validate Parameters: Check if there are any parameters passed incorrectly during the eviction process, such as specifying a node that is still in use.
- Confirm Object Types: Verify that the correct type of object (node) is targeted for eviction and that it is part of the cluster.
How to Resolve
- Correct Parameter Usage: Ensure all parameters are correctly specified, including the target node name or ID.
- Adjust Operation Context: If the node is active due to ongoing operations, wait until those operations complete before attempting the eviction again.
- Restore Data: If data corruption or misconfiguration caused the issue, restore the correct state of the cluster and retry the operation.
Developer Notes
Developers should be aware that this error can occur during planned maintenance activities such as node decommissioning or when troubleshooting issues within a cluster environment. Proper planning and validation are crucial to avoid encountering this error.
Related Errors
ERROR_NODE_NOT_FOUND(2036): Indicates the specified node does not exist in the cluster.ERROR_INVALID_PARAMETER(1258): Occurs when an invalid parameter is passed during a command or operation.
FAQ
Q: What causes this error?
A: This error occurs when attempting to evict an active node from a Windows Failover Cluster, as the node cannot be removed while it is still in use.
Q: Can I force the eviction of a node?
A: No, forcing the eviction can lead to service disruptions. It is recommended to ensure all services are stopped and the node is no longer active before attempting the operation.
Summary
ERROR_CANT_EVICT_ACTIVE_NODE (5009) is a specific error in Windows cluster environments that indicates an attempt to evict an active node from the cluster has failed. This error ensures the stability of the cluster by preventing the removal of nodes that are still performing critical functions. Proper planning and validation are essential to avoid this error and ensure the smooth operation of the cluster.