Export (0) Print
Expand All
Expand Minimize

MSExchangeIS 9518 (0xfffffd9a): Missing Checkpoint File, and More Than 1,008 Transaction Log Files Exist

[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]  

Topic Last Modified: 2009-09-23

The Microsoft® Exchange Database Troubleshooter Tool detected one or more MSExchangeIS 9518 events with error code 0xfffffd9a in the Application log. This error indicates that the checkpoint file (Exx.chk) for this storage group is missing or deleted, and there are more than 1,008 transaction log files to be played into the database.

This issue may occur if the following conditions are true:

  • The log files and databases are shut down correctly. Therefore there is no crash to recover from.

  • You rename or delete the Exx.chk checkpoint file.

  • There are more than 1,008 log files between checkpoints to replay on the server.

  • In a "roll-forward" recovery, one or more databases in the storage group are lost, but the log files remain intact on the server at the time of recovery. The "roll-forward" recovery operation is not completed successfully.

In this situation, the Microsoft Exchange Information Store service performs a soft recovery and replays all log files during startup. Because the log files and the database were shut down correctly, there is no recovery to perform. Because there is no checkpoint, Exchange processes all the logs until it reaches a record of a clean shutdown. Because there are more than 1,008 log files, Exchange reaches the limit of 1,008 log files before it can locate the record of a Clean Shutdown state.

noteNote:
The symptoms described may also occur if the conditions listed earlier are true, and you replay the log files by using the eseutil /r command. The eseutil /r command also performs a soft recovery on the mailbox store.

The error can also be identified as error JET_errCheckpointDepthTooDeep, -614. This error applies to Microsoft Exchange Server 2003 only.

To resolve this issue in Exchange Server 2003, apply Exchange 2003 SP1 or a later version.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft