The Microsoft Exchange Replication Service encountered an error while inspecting the logs and database for %1 on startup. The specific error code returned is: %2.

Details
Product: Exchange
Event ID: 2070
Source: MSExchangeRepl
Version: 8.0
Symbolic Name: FileCheckError
Message: The Microsoft Exchange Replication Service encountered an error while inspecting the logs and database for %1 on startup. The specific error code returned is: %2.
   
Explanation

This Error event indicates that the Microsoft® Exchange Replication (MSExchangeRepl) service produced an unrecoverable error and replication went into a failed state when the service inspected logs and database files. The error code string gives a more specific description of the problem. The error can occur when the replication service finds inconsistencies between the disk volume that contains the active copy of the storage group logs and database files and the disk volume that contains the passive copy of the storage group logs and database files.

These inconsistencies can occur for either of the following reasons:

  • There is an incorrect configuration. For example, the local continuous replication (LCR) copy directories point to the wrong location.

  • Physical storage is incorrectly mapped into the file system space. For example, you changed the drive mapping so that drive M is now mapped to drive N and drive N has a different set of data than what should be associated with it.

   
User Action

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

  • Make sure that the disk volumes of the active and passive copies of the storage groups are configured correctly.

  • Check the LCR configuration to make sure that the copy paths are correct. For more information, see How to View Local Continuous Replication Configuration Settings.

  • Make sure that the cluster continuous replication (CCR) network share is configured correctly. You can do this if you examine the log directory and remove the share. It will be automatically recreated after you run the Resume-StorageGroupCopy cmdlet from the Exchange Management Shell. For more information about how to run this cmdlet, see Resume-StorageGroupCopy.

  • If all these options fail, remove all log files and the database files from the passive node and re-seed the storage group copy on the passive node. For more information about how to seed, see the following topics:

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