Event ID 1024 — Registry Checkpointing

Event ID 1024 — Registry Checkpointing

Updated: December 5, 2007

Applies To: Windows Server 2008

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.0
Symbolic Name: CP_REG_CKPT_RESTORE_FAILED
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.

Resolve
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.

Verify

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

Related Management Information

Registry Checkpointing

Failover Clustering

Related:

Event ID 1024 — Remote Desktop Session Host Listener Availability

Event ID 1024 — Remote Desktop Session Host Listener Availability

Published: January 8, 2010

Applies To: Windows Server 2008 R2

The listener component runs on the RD Session Host server and is responsible for listening for and accepting new Remote Desktop Protocol (RDP) client connections, thereby allowing users to establish new remote sessions on the RD Session Host server. There is a listener for each Remote Desktop Services connection that exists on the RD Session Host server. Connections can be created and configured by using the Remote Desktop Session Host Configuration tool.

Event Details

Product: Windows Operating System
ID: 1024
Source: Microsoft-Windows-TerminalServices-RemoteConnectionManager
Version: 6.1
Symbolic Name: EVENT_TS_SESSDIR_FAIL_INIT_TSSD
Message: TermService clustering failed to initialize because the Session Directory Provider failed to initialize, hresult=%1.

Resolve

This is a normal condition. No further action is required.

Related Management Information

Remote Desktop Session Host Listener Availability

Remote Desktop Services

Related:

Failed to delete key with path {path} from metabase. Error code is {error code}.

Details
Product: Exchange
Event ID: 1024
Source: MSExchangeMU
Version: 6.0
Component: Metabase Update Service
Symbolic Name: DSMBLOG_DEL_KEY_FAILED
Message: Failed to delete key with path {path} from metabase. Error code is {error code}.
   
Explanation
The Metabase Update agent failed to delete a key in the Metabase. This may be a temporary error. If so, the Metabase will eventually recover from this error and the Metabase Update agent will update the Metabase properly.
   
User Action
No user action is required.If the problem persists, verify that the IIS Admin Service is running properly.For more information about the error code reference specified in the message, go to www.reskit.com.

Related:

%1: Failed to stop service ‘%2’.

Details
Product: Exchange
Event ID: 1024
Source: MSExchangeCluster
Version: 6.5.7596.0
Message: %1: Failed to stop service ‘%2’.
   
Explanation

This Error event is logged when the Microsoft® Exchange Cluster Service cannot stop the Microsoft Exchange service specified in the event description. This occurrence of MSExchangeCluster event 1024 is not enough to determine the root cause of this error.

   
User Action

To resolve this event, try one or more of the following:

  • Examine the Application log and System log for events that occur before and after this event. These related events may provide additional information that can help you determine the root cause of this error.

  • Try to determine whether there is a problem with the service specified in the event description. For information about troubleshooting a specific Exchange service, search the Microsoft Knowledge Base.

  • Stop all non-essential services on the Exchange Server computer that is logging this error. For example, stop the services that interact with Exchange such as antivirus applications or e-mail filtering services. If an MSExchangeCluster event 1024 does not occur after stopping these non-essential services, try to identify the specific service that is causing this error.

  • Make sure that you are running the most current Exchange Server 2003 updates and service packs. For information about Exchange Server updates and Service Packs, see Microsoft Knowledge Base article 906669, Issues that are fixed in Exchange Server 2003 Service Pack 2.

Related:

The connection to the ADAM instance of the Edge Transport server failed with exception “%1”. This could be caused by a failure to resolve the Edge Transport server name %2 in DNS, a failure when trying to connect to port %3 on Edge Transport server %2, network connectivity issues, an invalid certificate, or an expired subscription. Verify the configurations of your network and server.

Details
Product: Exchange
Event ID: 1024
Source: MSExchange EdgeSync
Version: 8.0
Symbolic Name: EdgeLeaseException
Message: The connection to the ADAM instance of the Edge Transport server failed with exception “%1”. This could be caused by a failure to resolve the Edge Transport server name %2 in DNS, a failure when trying to connect to port %3 on Edge Transport server %2, network connectivity issues, an invalid certificate, or an expired subscription. Verify the configurations of your network and server.
   
Explanation

This Warning event indicates that an exception occurred when the computer that is running the Hub Transport server role tried to acquire a lock on the computer that is running the Edge Transport server role. A lock is required to make sure that configuration data is correctly replicated to an Active Directory Application Mode (ADAM) instance on Edge Transport servers. ADAM can only be replicated with configuration data from one Hub Transport server at a time.

This event may be logged because a subscription on an Edge Transport server is expired or disabled. The exception specified in the event description provides more information about this failure.

   
User Action

To resolve this event, re-subscribe the Edge Transport server specified in the event description. For more information, see Subscribing the Edge Transport Server to the Exchange Organization.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

was unable to log on as to the Public Folder Store “”.

Details
Product: Exchange
Event ID: 1024
Source: MSExchangeIS
Version: 6.5.6940.0
Component: Microsoft Exchange Information Store
Message: <user name> was unable to log on as <user name> to the Public Folder Store “<name>“.
   
Explanation

The message text in the Description section of this event is similar to: NT AUTHORITY\SYSTEM was unable to log on to the public store as NT AUTHORITY\SYSTEM. NT AUTHORITY\SYSTEM is the local system account, which is the account used in Exchange 2000 or greater to start all the Exchange services. This error means that the local system account is unable to log on to the named public folder store database on the server named in the event. The causes for this event are varied. In some cases, there is a permissions problem. In other cases, the database itself is unavailable to be logged on to, for various reasons. Here are some examples of known causes of this event:

  • The public store has been removed and the Exchange store has been started in order to create a blank public information store, but the database has not been mounted yet.
  • The “create top level public folder” permission for the Everyone group within Security tab of the Public Folders object in Exchange System Manager has been set with an explicit deny.
  • A problem during the upgrade of the Access Control Lists (ACLs) of public folders that were migrated to Exchange 2000 or greater from Exchange 5.5 causes the public store database to be unavailable for logon. This occurrence may be an associated MSExchange Event IDs 9551, 9548, or 9562 which reference specific errors upgrading the ACL on a public folder. This occurrence may or may not be associated with an MSExchangeIS Event ID 1165, which is an event that is a notification that the Exchange store does not have enough database sessions for the threads in the store process that are servicing client requests. Whenever this occurs, performance will be adversely affected.
   
User Action

Generally, check for related events in the application log to determine the root cause of why the local system account cannot log on to the public store. A few resolutions are as follows.

  • Use Exchange System Manager (ESM) to mount the public information store database and a new, blank public information store will be created.
  • To determine how the permissions are set, run the DSACLS utility from the command line. NOTE: DSACLS is a command-line utility that is included with Microsoft Windows 2000 Server and is installed when you install the Windows 2000 Support Tools. Remove the assigned Deny permission using DSACLS.
  • Check the application log for errors that relate to public folder expansion problems such as Event IDs 9551, 9448, and 9562. Also check for the presence of Event ID 1165. Check the Microsoft Knowledge Base for the latest information on how to resolve these errors. Make sure that the latest Exchange service pack is installed. Check for any post-service hotfixes that resolve public folder expansion symptoms.

Related: