Fix Database recovery failed with error -1216 in Exchange Server

When the Exchange server database gets corrupt due to reasons like unexpected system shutdown, virus attack, software or application malfunction, missing database objects etc. you have the option to go for a repair utility called as Eseutil provided by Exchange server which works to detect and repair the corruption issues as well as defragment the hard drive. But this tool does not prove to be useful in the cases of severe corruption which lead to errors like Database recovery failed with error -1216 and then the need arises for edb repair tool.

Assume a situation where you are trying to repair damaged Exchange server database using Eseutil command but instead of got the following entries in Application event log:

"Event Type: Information

Event Source: ESE

Event Category: Logging/Recovery

Event ID: 301

Date: 29-08-2003

Time: 13:44:26

User: N/A

Computer: SNUCKERSERVER Description: Information Store (2040) 8f47d891-b071-466b-b70d-ae123f886ea6: The database engine has begun replaying logfile C:\Program Files\Exchsrvr\mdbdata\E00.log."

Or

"Event Type: Error

Event Source: ESE

Event Category: Logging/Recovery

Event ID: 494

Date: 29-08-2003

Time: 13:44:27

User: N/A

Computer: SNUCKERSERVER

Description: Information Store (2040) Database recovery failed with error -1216 because it encountered references to a database, ‘C:\Program Files\Exchsrvr\mdbdata\priv1.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 main reason behind the occurrence of the database recovery failed with error exchange is the incapability of Eseutil command to repair the database. So, it would be better to go for Microsoft Exchange Server Edb Repair tool that works to repair the database corruption issues even in severe cases without much intervention of users. It helps in restoration of the entire Exchange contacts recovery and ultimately database recovery failed because it encountered references error gets resolved in minutes.