support@exchangeserverrecovery.com 1-866-348-7872
<--nav-->
<--nav end-->
Exchange Server

Resolve Exchange Error: 1216 JET_errAttachedDatabaseMismatch

Resolve Exchange Error: 1216 JET_errAttachedDatabaseMismatch

Exchange Server, which stores user mailboxes and its items, sometimes face different types Exchange Server Jet errors that make the Exchange database inaccessible. In this blog we will discuss Exchange Server Jet Engine error code: 1216.

What is Jet error 1216? What are the reasons for its occurrence? And what are the resolutions of this error?

What is Jet Engine error: 1216?

This error sometimes encountered when administrators try to mount a backup database to Exchange server:

“Error -1216 (JET_errAttachedDatabaseMismatch)”

This error clearly indicates that the of Exchange Server database restore is failed. And the description of this error clearly defines that, “Database recovery of Exchange is failed with Jet Engine error-1216. This is a critical situation because there are chances of permanent data loss.

How Jet Engine Error: 1216 occurs in Exchange Server

This error occurs when an administrator tries to restore a backup of Offline Exchange database files without meeting the conditions for “Point in time” restoration and “Roll forward” restoration:

  • Point in time of Restoration:If you want to restore your database with this method, then you have to make sure that database is consistent, all logfiles are present, and the database has valid checkpoints. If all these conditions are met, then your database will be successfully restored; otherwise you will face error 1216.
  • Roll forward Restoration:If you want to restore your database with this method, then you have to make sure that the checkpoint file is deleted. But valid transaction logs which were created after the backup must exist. If all the conditions are fulfilled, then your database can be restored successfully.

How to fix Jet Engine Error 1216
If you want to fix this JET engine error 1216, then you have first check whether your database is damaged or not. For this you need to verify the checkpoints in above two :

  • Point in time of Restoration:In this method, to verify the checkpoints, you have to run the below-mentioned command:
    eseutil /mk e00.chk | find /i “checkpoint”
    eseutil /ml E0n.log | FIND /i “generation“.
  • Roll forward Restoration:To verify checkpoints in Roll forward Restoration, you have to run the below-mentioned command:

    eseutil /mh database_file_name | find /i “consistent”
    eseutil /mh database_name | find /i “Shutdown”

    If you find any invalid checkpoint and your database is damaged, then you have to use a third party tool to repair it.

Exchange Recovery Manager

The Exchange Recovery Manager software is an intelligently designed tool which can repair damaged EDB files; you can quickly repair your damaged Exchange database (EDB) files and export them to PST files. With this tool, you can migrate your dismounted EDB file to Live Exchange and Office 365 as well. The EDB to PST Converter tool allows you to migrate your mailboxes, public folder and archive mailboxes to the desired destination. You can extract attachments, drag and drop emails and copy-paste mailboxes with this tool. This tool is reliable for non-technical users as well.