Getting Exchange error ‘JET_errLogCorruptDuringHardRestore’?

Have you experienced the situation of dirty shutdown with MS Exchange Server? You must have encountered such a situation because it’s very common and tends to happen. After dirty shutdown of Exchange Server, when you try to mount the Information Store database(s) next time, it fails and you receive errors suggesting that one or more database(s) are corrupt. On performing hard restore using backup copy everything fails and you get something like,

“JET_errLogCorruptDuringHardRestore -573”

Error – 573 indicates that Exchange Server has detected some corruption in a backup set; therefore you fail to proceed further.

Solution

To solve this problem, try the following methods.

1. Check for some other valid and updated backup set that may be used to restore the database and carry out hard restore.
2. If not successful with it, then run ‘ESEUTIL /P database_filename.edb’ command to repair the database, where ‘database_filename’ is the name of the corrupted database file.

Using ESEUTIL utility can discard table rows and even complete tables. So, it would be better if you perform recovery of Exchange database with backup copy.

Last but not the least, if backup thing doesn’t work, go for third party software to get efficient Exchange database recovery. Exchange recovery software repairs corrupt database (.EDB) file to recover mailboxes safely from them. The software rebuilds the entire EDB database which can be easily mounted to MS Exchange server.

Comments are closed.