subject: Error 1216 Logs When One Or More Database Files Are Inconsistent [print this page] Exchange Server database files are the most important recovery elements, required to be rebuilt after information store crash. If you can successfully restore them from the last backup and all required transaction log files are available, you should replay them to get the database to the state that existed before the crash occurred. In case of any issues, eseutil repair utility can help, but can cause data loss. For safe database repair, use of Exchange Server Recovery software is recommended. These tools can diagnose and repair all database contents using advanced procedures.
For instance, you might observe that Exchange Server storage group stops unexpectedly. If this leaves few database files unavailable for the server, you encounter the below error marked in the Application event log:
Information Store (4312) Database recovery failed with error -1216 because it encountered references to a database, 'D:exchsrvrmdbdataPRIV2.edb', which is no longer present. The database was not brought to a consistent state before it was removed (or possibly moved or renamed). The database engine will not permit recovery to complete for this instance until the missing database is re-instated. If the database is truly no longer available and no longer required, please contact PSS for further instructions regarding the steps required in order to allow recovery to proceed without this database.
The corresponding event is logged with Event ID '0'.
Cause
All or few database files of storage group are inconsistent.
Solution
You can check the database file consistency by running Eseutil /mh command. If you find any database inconsistent, you should apply these methods to recover:
1.Restore from backup. You can determine the logs required by executing eseutil /mh database_name | find /i "log required command. Play the log files, if available
2.Perform hard repair using eseutil /p command, followed by eseutil /d and isinteg -fix commands
3.If the database contains no important information, you can simply delete it and create a new one
4.Corrupted database files can be safely repaired using Exchange Recovery products. Exchange Server Recovery applications are powerful tools that employ high-end scanning algorithms to repair damaged Exchange databases and provide you interactive interface to work with.
Stellar Phoenix Mailbox Exchange Recovery is a fully-features tool to safely extract all the mailboxes from damaged databases created with Exchange Server 5.5, 2000 and 2003. It is a non-destructive Exchange Recovery product that can restore all objects including emails, email properties, tasks, drafts and more.
