How to fix “The cluster node was evicted from the cluster successfully but the node was not cleaned up. To determine what cleanup steps failed and how to recover see the Failover Clustering application event log using Event Viewer. [ERROR_CLUSTER_EVICT_WITHOUT_CLEANUP (0x1708)]” – Error Code 5896


lightbulb

Error Code 5896

Error code Error Code 5896 is a common Windows issue that typically arises from “The cluster node was evicted from the cluster successfully but the node was not cleaned up. To determine what cleanup steps failed and how to recover see the Failover Clustering application event log using Event Viewer. [ERROR_CLUSTER_EVICT_WITHOUT_CLEANUP (0x1708)]”.

Overview

In this article, we’ll focus on resolving the issue described as: “The cluster node was evicted from the cluster successfully but the node was not cleaned up. To determine what cleanup steps failed and how to recover see the Failover Clustering application event log using Event Viewer. [ERROR_CLUSTER_EVICT_WITHOUT_CLEANUP (0x1708)]”. This error, identified by the error code Error Code 5896, can impede your system’s performance, and here’s how you can fix it.

Identifying the Problem

What is Error Code 5896?

Error Code 5896, also known as ERROR_CLUSTER_EVICT_WITHOUT_CLEANUP, occurs when Failover Clustering fails to clean up a node successfully after it has been evicted from the cluster. The system may display the error message “The cluster node was evicted from the cluster successfully but the node was not cleaned up. To determine what cleanup steps failed and how to recover see the Failover Clustering application event log using Event Viewer.”

Typical Scenarios

This error typically appears:
– During the eviction of a cluster node
– After upgrading to a newer version of Windows Server

Signs of Error

The error can manifest in several ways, including:
– System performance degradation
– Cluster services not functioning properly
– Node eviction failing repeatedly

Common Fixes

Method 1: Check Event Viewer Logs

  • Open Event Viewer (Start > Event Viewer)
  • Navigate to “Applications and Services Logs” > “Microsoft” > “Windows” > “FailoverClustering” > “Operational”
  • Check for events related to Error Code 5896. The logs will provide details on the failed cleanup steps.

Method 2: Restart Cluster Service

  • Open Services (Start > Search for “Services.msc”)
  • Locate the “Cluster Service” and right-click on it
  • Select “Restart” and wait for the service to restart

Method 3: Run Windows Deployment Image Servicing and Management (DISM)

  • Open an elevated Command Prompt (Start > Search for “cmd” > Right-click “Command Prompt” > “Run as administrator”)
  • Run the command: DISM /Online /Cleanup-Image /RestoreHealth
  • Wait for the DISM operation to complete

Advanced Troubleshooting

Method 4: Check Cluster Configuration

  • Verify if the shared storage is accessible to all cluster nodes.
  • Ensure that the network configuration is correct and that there are no firewalls blocking cluster communication.

Method 5: Repair Windows System Files

  • Open an elevated Command Prompt
  • Run the command: sfc /scannow
  • This command will scan and repair any corrupted system files.

Method 6: Reinstall Cluster Service

  • Uninstall the Cluster Service from all nodes in the cluster.
  • Reboot the nodes.
  • Install the Cluster Service on all nodes again.
  • Recreate the cluster.

Conclusion

Error Code 5896 can be resolved using the methods outlined in this article. By carefully following the steps, you can troubleshoot and fix this error effectively. Additionally, implementing preventive measures such as regular system maintenance and updates can help avoid future occurrences of this error.