Node Cleanup Success
Applies To: Windows Server 2008 R2
When a failover cluster is destroyed by running the Destroy Cluster command, the Cluster service requires access to disks in storage and other resources for complete removal of the cluster configuration. If this access is unavailable, you might need to take specific actions such as running a command to complete the removal of the configuration.
Events
| Event ID | Source | Message |
|---|---|---|
Microsoft-Windows-FailoverClustering |
Cluster service failed to retrieve the list of clustered disks while destroying the cluster. The error code was '%1'. If these disks are not accessible, execute the 'Clear-ClusterDiskReservation' PowerShell cmdlet. | |
Microsoft-Windows-FailoverClustering |
Clustered disk with ID '%2' was not released by the Partition Manager while destroying the cluster. The error code was '%1'. Restarting the machine will ensure the disk is released by the Partition Manager. | |
Microsoft-Windows-FailoverClustering |
The cluster service failed to properly cleanup a clustered disk with ID '%2' while destroying the cluster. The error code was '%1'. You may unable to access this disk until cleanup has been successfully completed. For manual cleanup, delete the 'AttachedDisks' value of the 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ClusDisk\Parameters' key in the Windows registry. | |
Microsoft-Windows-FailoverClustering |
Disabling the cluster service during cluster node cleanup, has failed. The error code was '%1'. You may be unable to create or join a cluster with this machine until cleanup has been successfully completed. For manual cleanup, execute the 'Clear-ClusterNode' PowerShell cmdlet on this machine. | |
Microsoft-Windows-FailoverClustering |
Termination of the cluster service during cluster node cleanup has not completed within the expected time period. Please restart this machine to ensure the cluster service is no longer running. | |
Microsoft-Windows-FailoverClustering |
Resetting cluster service registry entries during cluster node cleanup failed. The error code was '%1'. You may be unable to create or join a cluster with this machine until cleanup has been successfully completed. For manual cleanup, execute the 'Clear-ClusterNode' PowerShell cmdlet on this machine. | |
Microsoft-Windows-FailoverClustering |
Unloading the cluster service registry hive during cluster node cleanup failed. The error code was '%1'. You may be unable to create or join a cluster with this machine until cleanup has been successfully completed. For manual cleanup, execute the 'Clear-ClusterNode' PowerShell cmdlet on this machine. | |
Microsoft-Windows-FailoverClustering |
Cluster node cleanup encounted at least one error. You may be unable to create or join a cluster with this machine until cleanup has been successfully completed. Please review and resolve preceding cluster node cleanup events. For manual cleanup, execute the 'Clear-ClusterNode' PowerShell cmdlet on this machine. | |
Microsoft-Windows-FailoverClustering |
Resetting the IPSec security association timeout registry value failed during cluster node cleanup. The error code was '%1'. For manual cleanup, execute the 'Clear-ClusterNode' PowerShell cmdlet on this machine. Alternatively, you may reset the IPSec security association timeout by deleting the '%2' value and the '%3' value from HKEY_LOCAL_MACHINE in the Windows registry. | |
Microsoft-Windows-FailoverClustering |
Resetting the IPSec security association timeout registry value failed during cluster node cleanup. This is because the IPSec security association timeout was modified after this machine was configured to be a member of a cluster. For manual cleanup, execute the 'Clear-ClusterNode' PowerShell cmdlet on this machine. Alternatively, you may reset the IPSec security association timeout by deleting the '%1' value and the '%2' value from HKEY_LOCAL_MACHINE in the Windows registry. |