Remove the Edb.chk file, and then restart the database service.
If the Edb.chk file is gone, Exchange Server scans through all the available log files, and then begins recovery using the first log file that it finds.
Cautions
Do not remove the Edb.chk file unless you know exactly why you need to remove it, and unless you know that you can safely remove it in your current circumstances. Removing the Edb.chk file in certain circumstances may irreparably damage the database.
For more information about the checkpoint, click the following article number to view the article in the Microsoft Knowledge Base:
240145�
How to remove Exchange Server transaction log files
If you are experiencing the conditions described here, and if all of the following statements are true, you can safely delete the Edb.chk file:
- You have not moved, renamed, deleted, replaced, or otherwise tampered with the database or transaction logs after the abnormal shutdown. For recovery to succeed, the database and transaction logs must be in exactly the same state that they were in when the database stopped.
- If you ran the eseutil /r command against the database, and you used the /is or /ds switches to run it. (The eseutil /r /is command is for the information store, and the eseutil /r /ds command is for the directory service.)
If you omit the /is or /ds switches, the soft recovery assumes that the log files are in the folder that you ran Eseutil from. If the log files are elsewhere, as they usually are, soft recovery creates a new Edb.log file and tries to recover against the wrong set of log files. You
can still delete the Edb.chk file after such an event, but the database still may not start, and you may need to restore it from a backup.
- You have circular logging enabled. If circular logging was disabled at the time of the abnormal shutdown, none of the recommendations in this article apply. If circular logging is disabled, transaction log files are not automatically deleted when the checkpoint advances. This means that the cause of the restart problem is different than the cause described here.