Fixed: Exchange Server Jet Error 1216 (JET_errAttachedDatabaseMismatch)

Exchange Jet Error 1216 is amongst the most common issues which anonymously occur when you try to mount database in Exchange Server, and unluckily you encounter the error message:

'Error -1216 (JET_errAttachedDatabaseMismatch)'

Other possible reasons could be lost or corrupt Exchange database files, network problems, or some important files which are required to work Exchange Server, has been deleted or altered! 

In another scenario, if you notice storage group stops working all of sudden, then it is also possible all of the Exchange mailbox database will become inaccessible and inconsistent. In the case, you will find the following error message in the event log of the application-

“Event Type: Error

Event Source: ESE98

Event Category: Logging/Recovery

Event ID: 0

Date: 7/8/2015

Time: 9:23:56 AM

User: N/A

Computer: LocalExchange

Description: Information Store (4312) Database recovery failed with error -1216 because it encountered references to a database, ‘C:\ localexchange \mdbdata\PRIV3.edb’, which is no longer present. The database was not brought to a consistent state before it was removed (or possibly moved or renamed)” 

Now you can easily find out whether the file is renamed or missing, else the file is become inconsistent.

So below I am sharing few quick methods to fix Exchange server jet error message.

How to Fix Exchange Server Error -1216

Eseutil is really an excellent inbuilt utility in Exchange Server which can be used to resolve the issue by running the below commands against the file.

Run the below command to recognize either the file is inconsistent or not-

eseutil /mh name_of_database | find /i "consistent"

If you’re running Exchange Server 2010/2007/2003, check the state of the database file by executing the below command-

eseutil /mh name_of_database | find /i "Shutdown"

Now you can check the returned output and run the Eseutil command to repair the database file. But before executing the commands (Eseutil/P, Eseutil/d, after that isinteg -fix), make sure that all of the logs must be available to effectively repair and recover the database.

But it case if the Eseutil fails to repair the database, you may encounter the following error message-

Operation terminated with error -1216 (JET_errAttachedDatabaseMismatch, An outstanding database attachment has been detected at the start or end of recovery, but database is missing or does not match attachment info) after 2.551 seconds.

So if Eseutil is unable to help you out, you need a prominent tool for troubleshooting Exchange server Jet Error codes, and repairs & recover Exchange Server database.

Try Stellar Phoenix Mailbox Exchange Recovery software to resolve 1216 Jet Error, and restore the inaccessible mailbox database from inconsistent state. You can also repair and recover corrupt or lost mailbox from .edb file using this utility. For more information, you can download and check the features of this software here at: http://www.stellarservertools.com/recover-exchange-mailbox.php

Please revert if you have further queries on the discussed error.

Thanks,