Exchange Mailbox Recovery

Exchange Mailbox Recovery Software

MS Exchange Server creates communication network in the multi-user environment. It has been extensively used in IT sector for internal as well as external email communication. MS Exchange Server stores mailboxes of IMAP1 or POP3 clients in several EDB databases. EDB database updates Exchange mailbox information of users and ensures smooth email services in large organization. Exchange Server mailbox corruption cripples emailing activities in the Exchange based organization. You might encounter various error messages while trying to open an Exchange mailbox. One frequently encountered Exchange mailbox error message is:

Error 4294966746: JET_errDatabaseInconsistent

This error message will be displayed if a mailbox store or public store of MS Exchange Server has been damaged. There might be various reasons of Jet error code 4294966746:

  • Hard disk bad sectors
  • Improper shutting down of MS Exchange Server
  • Virus or spyware codes
  • Windows crash


Microsoft has provided two command tools i.e., Eseutil.exe and Isinteg.exe to fix Exchange mailbox corruption. Before using inbuilt Exchange recovery tools, you must analyze the event logs generated along with Jet error code 42966746. It will help you in knowing about the EDB folder that has reported Jet database error code. You should run Eseutil/mh command to check the integrity of the corrupt EDB folder (mailbox store or public store):



  • Eseutil/mh “C:\Program Files\Exchsrvr\MDBData\A001mystars.EDB”

.If the above command reports A001mystars.EDB in clean shutdown state, then it can be assumed that the database is consistent with Transaction logs. In such situation, you must copy the Transaction logs of an Exchange information store to another disk location and remount the A001mystars.EDB file on the Exchange Server.

.If the Eseutil/mh command states A001mystars.EDB file in dirty shutdown state, it can be assumed that database and Transaction logs of an Exchange mailbox Store /Public Store are inconsistent. Exchange Server dirty shutdown situation might be generated due to missing or corrupt transaction logs. You must ascertain the status of the Transaction log files using Eseutil/ml command. If the Transaction log files are in clean shutdown state, start recovering the corrupt database A001mystars.EDB for example using following command:

  • Eseutil/r E01/l “C:\Program Files\Exchrvr\MDBDATA” /d “C:\Program Files\Exchrvr\MDBDATA\A001mystars.EDB”

After repairing corrupt A001mystars.EDB file with Eseutil command, mount the database folder on the Exchange Server.

You can also use Eseutil/p command to recover corrupt EDB file in case some transaction logs has been missing or damaged. The Eseutil/P command line to recover corrupt A001mystart.EDB file will be be:

  • Eseutil/P “C:\Program Files\Exchrvr\MDBDATA\A001mystars.EDB”

You must also defragment the recovered EDB folder and then run Isinteg command before putting that database back onto the mail Server.

  • Isinteg [“A001mystars.EDB”] [-fix]

But both Eseutil and Isinteg commands can be applied on offline EDB stores only. Moreover, inbuilt Exchange recovery tools fails to fix many critical Exchange Server issues. It is therefore, better to use a professional Exchange mailbox recovery tool to fix Exchange corruption.

RecoveryFix for Exchange Server is a sophisticated edb to pst tool to cure Exchange Server disasters. It is capable of retrieving Exchange mailboxes from the large EDB folder. Exchange mailbox recovery software is equipped with three powerful recovery modes i.e., Automatic Analyze and recover, Advance Scan and Rebuild corrupt database. restores inaccessible Exchange Server mailboxes in PST or EDB file format. Exchange mailbox recovery software supports MS Exchange Server 2000, 2003, 2007 and 2010.