This article was previously published under Q307469
After you restore the Cluster service on a Microsoft Windows Server 2003 or Windows 2000-based server cluster, the registry check pointing feature of Windows clustering may stop functioning.
Additionally, you may receive one of or all the following event messages in the System log of the Event Viewer:
Source: ClusSvc Event ID: 1024 Description: The registry checkpoint for cluster resource %ResourceName% could not be restored to registry key HKLM\system\currentcontrolset\services\%ServiceName%. The resource may not function correctly. Make sure no other processes have open handles to subkeys in the registry subtree.
Source: ClusSvc Event ID: 1082 Description: The Microsoft Clustering Service failed restore a registry key for resource %ResourceName% when it was brought online. This error code was <NTSTATUS>. Some changes may be lost.
Source: ClusSvc Event ID: 1080 Desription: The Microsoft Clustering Service could not write file (C:\DOCUME~1\exmscs\LOCALS~1\Temp\CLSxxx.tmp). The disk may be low on disk space, or some other serious condition exists.
This behavior may occur when you restore the Cluster service by using the -resetquorumlog parameter.
To resolve this behavior, reset the server cluster check points by using the Windows Server 2003 ClusterRecovery utility. To obtain this utility, visit the following Microsoft Web site:
In earlier versions of Windows server clusters, resetting the check points is more complex. With Windows Server 2003, the ClusterRecovery utility (ClusterRecovery.exe) restores the check points much faster. This utility is included with the Microsoft Windows Server 2003 Resource Kit and is also ported (backported) to Microsoft Windows 2000 Server. For additional information about how to use the ClusterRecovery tool to reset server cluster check points, view the ClusterRecovery.chm help file that is included with the ClusterRecovery.exe program.