Process %1 (PID=%2). Failed to flush Kerberos ticket for local system account – Error code=%3. Microsoft Exchange AD Topology service could not update token to have Exchange Servers group membership (SID: %4). This may be caused by replication latency. Wait for replication to complete and try again.

Details
Product: Exchange
Event ID: 2602
Source: MSExchange ADAccess
Version: 8.0
Symbolic Name: ADTOPO_RPC_FLUSH_TICKET_FAILED
Message: Process %1 (PID=%2). Failed to flush Kerberos ticket for local system account – Error code=%3. Microsoft Exchange AD Topology service could not update token to have Exchange Servers group membership (SID: %4). This may be caused by replication latency. Wait for replication to complete and try again.
   
Explanation

This Error event indicates a failure to add the Exchange Servers universal security group in the process token. A process token is used by the Microsoft Exchange Active Directory Topology service to establish a session with the Active Directory server. This event may occur because of replication delays between the Active Directory servers. This event may also occur while you are running Microsoft Exchange Server 2007 Setup. It may occur during setup because replication delays may occur while the Active Directory schema is updating.

   
User Action

To resolve this error, follow one or more of these steps:

  • Make sure that Active Directory replication is working correctly. For more information about Active Directory replication and how it works, see “Active Directory Replication Topology” in Active Directory Replication Technologies.

  • Check the group membership of the Exchange Servers group in the root domain and make sure the computer account is not shown as disabled. If the computer account is shown as disabled, delete, and then add the computer account again. For more information about preparing Active Directory and domains, see How to Prepare Active Directory and Domains.

  • Review related Error and Warning events in the Application log. These events may help you find the root cause of this event.

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:

Leave a Reply