Event ID 4624 — Node Cleanup Success

  • Article

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.

Event Details

Product: Windows Operating System
ID: 4624
Source: Microsoft-Windows-FailoverClustering
Version: 6.1
Symbolic Name: NODECLEANUP_RESET_NLBSFLAGS_FAILED
Message: 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.

Resolve

Confirm that the action of destroying a cluster was fully completed

An operation that was part of destroying the cluster did not succeed. Try restarting the server to see if this resolves the error. If not, use commands to force cleanup on former cluster nodes, and to force the clearing of persistent reservations on disks formerly used by the cluster. These commands help ensure that the cluster configuration has been completely removed.

If you do not currently have Event Viewer open, see "Opening Event Viewer and viewing events related to failover clustering." If the event contains an error code that you have not yet looked up, see "Finding more information about error codes that some event messages contain."

To perform the following procedures, you must be a member of the local Administrators group on the server, or you must have been delegated the equivalent authority.

Forcing cleanup on a former cluster node after the cluster has been destroyed

To force cleanup on a former cluster node after the cluster has been destroyed:

  1. On the former cluster node that you want to clean up, open an elevated Command Prompt window. To do this, click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

  2. Type:

    CLUSTER NODE /FORCECLEANUP

Forcing the clearing of persistent reservations on a disk formerly used by the cluster

To force the clearing of persistent reservations on a disk formerly used by the cluster:

  1. On one or more nodes in the cluster, open Disk Management (which is in Server Manager under Storage) and see if any disks formerly used by the cluster are visible from one of the nodes. If they are, note the node and the number that Disk Management uses to refer to that disk. For example, if the disk is listed as Disk 4 in Disk Management, note the number 4.

  2. On a node from which a formerly-clustered disk is visible in Disk Management, open an elevated Command Prompt window. To do this, click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

  3. Type:

    CLUSTER NODE /CLEARPR:disknumber

    where disknumber is the number of the disk as it appeared in Disk Management.

To open Event Viewer and view events related to failover clustering:

  1. If Server Manager is not already open, click Start, click Administrative Tools, and then click Server Manager. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  2. In the console tree, expand Diagnostics, expand Event Viewer, expand Windows Logs, and then click System.
  3. To filter the events so that only events with a Source of FailoverClustering are shown, in the Actions pane, click Filter Current Log. On the Filter tab, in the Event sources box, select FailoverClustering. Select other options as appropriate, and then click OK.
  4. To sort the displayed events by date and time, in the center pane, click the Date and Time column heading.

Finding more information about the error codes that some event messages contain

To find more information about the error codes that some event messages contain:

  1. View the event, and note the error code.
  2. Look up more information about the error code in one of two ways:

Verify

To verify the cleanup of a cluster node, you can rerun the command for forcing cleanup and confirm that it completes successfully.

To perform the following procedure, you must be a member of the local Administrators group on the server, or you must have been delegated the equivalent authority.

To run the command that forces cleanup of a former cluster node:

  1. On the former cluster node on which you want to confirm cleanup, open an elevated Command Prompt window. To do this, click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

  2. Type:

    CLUSTER NODE /FORCECLEANUP

  3. View the results and confirm that node cleanup completed successfully.

Node Cleanup Success

Failover Clustering