This error is returned by the Exchange Server database engine when it
encounters a problem replaying log files on startup. Possible reasons for
the error are as follows:
- Missing Transaction Log Files.
When each service starts, it looks for its transaction log files to
replay any missing transactions. These log files are by default in the
DSADATA, MDBDATA, and DXADATA directories for the Directory, Information
Store, and Directory Synchronization services respectively. The location
of the log files for each service is configurable through the Exchange
Server Performance Wizard.
While replaying the transactions, if a transaction log file is missing,
the above error is returned. For example, suppose the DSADATA directory
contains the following transaction log files: EDB.LOG, EDB00001.LOG,
EDB00002.LOG, EDB00004.LOG, and EDB00005.LOG. It is missing the
EDB00003.LOG file. When the Directory Service starts replaying these
logs, it will start with EDB.LOG, then go to EDB00005.LOG and then
EDB00004.LOG. When it finds the log file EDB00003.LOG is missing it will
abort because it cannot proceed to file EDB00002.LOG without processing
EDB00003.LOG.
- One or more logs are inaccessible.
The log files are marked as read-only, are hidden, or the Exchange
Server service account does not have the necessary access rights.
- Not enough free disk space on the drive containing the databases.