Tuesday, August 29, 2017

Exchange Error 1216 JET_errAttachedDatabaseMismatch [RESOLVED]

Know How to Resolve Exchange Error 1216

The worst situation for the Exchange administrator is when Exchange EDB file gets corrupted or damaged. We all know that Exchange stores all its data in EDB format that can only be used via MS Outlook email applications without any issue. However, just like other file extensions, there are the conditions when EDB data files get corrupted and displays errors. One such error is Exchange Error 1216 JET_errAttachedDatabaseMismatch. Users facing this error have to face so many problems. So, in this blog, we are going to discuss the solutions to remove the specified error.

Usually, when the one gets Jet Error then, it is not manageable practically to utilize Exchange database files. However, these instances give out the result in data loss situation. In order, to get back the access of crucial data then, first figure out the main reason behind the issue. Out of which, one such error is:
"Exchange Error -1216 (JET_errAttachedDatabaseMismatch)"

Rapid Solution: SysTools Exchange Server Recovery is a complete solution that makes easy to recover all the corrupted or inaccessible data. The application is capable enough to fix Exchange Error JET_errAttachedDatabaseMismatch completely in a secure and reliable way. The utility retrieves all the data in exact form without losing a bit of data information.

Cause behind the Exchange Error 1216 JET_errAttachedDatabaseMismatch

This error is due to assessment of header information in log files. Moreover, databases displays that there has been the removal of files. If soft recovery is run for this error then, it may begin the storage group or it will left the storage group running with various missing of data files. If you execute soft recovery, it may be hard to include lost information into storage group. When the storage group starts, whether the earlier shutdown was unusual, information of header is inspected by machine; if the assessment of system files headers disclosures inconsistencies, a -1216 Jet error is returned.

Solution to Remove Exchange Error 1216

If the storage group simply stops all of sudden then, there are the chances that almost all database files become inconsistent. If issue leads to stoppage of storage group then, it leaves more than one database files unreachable. In that case, an error message is logged in event log of application.
One can simply identify the inconsistence of files by using ESEUTIL command against the files. eseutil /mh database_name | find /i "consistent" If you are utilizing higher edition of MS Exchange Server then, you can get the state of database file by simply executing the command as discussed below; eseutil /mh database_name | find /i "Shutdown"

Output you get after implementing the command

All the logs must be present for successful database recover but in case, any logs are missing. Then, you will not be able to do recovery of database. It will be left with no other option than doing the following: Migrate all database files, which are missing in the last Consistent logs to safe location. After that, restore the residual files by simply mounting them. Reinstate the database from backup Repair database. To execute this, you require executing eseutil /p command, eseutil /d command. After that, isinteg -fixing command. 

Summing Up

Getting an error message creates a hurdle in the working flow of any user. Therefore, in the above-discussion, we have discussed the most common error of Exchange and its solution, i.e. Exchange Error 1216 JET_errAttachedDatabaseMismatch. If you still face any issue then, feel free to drop a comment below. The problem will further be looked by the experts and provides you with appropriate solution over it.


Post a Comment

Post a reply