Event ID 1024 — Registry Checkpointing

Applies To: Windows Server 2008 R2

Some clustered services and applications store information outside of the cluster configuration database, in registry keys that the Cluster service monitors and replicates between nodes. If the Cluster service is prevented from writing to such a registry key, the corresponding cluster resource might not function correctly.

Event Details

Product: Windows Operating System
ID: 1024
Source: Microsoft-Windows-FailoverClustering
Version: 6.1
Message: The registry checkpoint for cluster resource '%1' could not be restored to registry key HKEY_LOCAL_MACHINE\%2. The resource may not function correctly. Make sure that no other processes have open handles to registry keys in this registry subtree.


Ensure that no application has an open handle to the registry checkpoint

Close any application that might have an open handle to the registry checkpoint indicated by the event. This will allow the registry key to be replicated as configured with the resource properties. If necessary, contact the application vendor about this problem.

You can use a utility called Handle with the -a option to view handles to the registry. For information and download instructions for Handle, see http://go.microsoft.com/fwlink/?LinkId=105134.

If you do not currently have Event Viewer open, see "To open Event Viewer and view events related to failover clustering."

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

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.


Retry the action that resulted in a problem with replication of a registry key between nodes, to confirm that any issues have been corrected.

Registry Checkpointing

Failover Clustering