Exchange Server Database corruption is one of the common and major problems of Microsoft Exchange Server. There are many issues which leads to the corruption of the Exchange database like human errors, hardware issues, virus infection, dirty system shutdown, EDB file header corruption, network issues and so on. All these factors leads to the corruption of EDB file which don't let you mount the Exchange Server. In these circumstances you need to search the main cause of corruption and need to perform appropriate action to repair the corrupt database.
When the Exchange Server database gets corrupt or damage, you should use the backup to restore the corrupt database or need to run ESEUTIL utility to repair it. ESEUTIL utility is located in the folder – C:\Program Files\Exchsrvr\Bin.
Now, consider that you run ESEUTIL /D utility to defragment your Exchange database but in the mean time the process failed and you encountered an error message in the Application Event Log file –
“Operation terminated with error -327 (JET_errBadPageLink, Database corrupted) after seconds”
After this error message, you will not be able to perform any normal operation on the database and your server will become unresponsive.
Cause
The JET_errBadPageLink error is indicating the logical corruption in the database and it may be the consequence of incorrect internal database structure.
Solution
In order to get rid of this error, you have to follow certain methods as mentioned below –
- First check for the backup if it is available, in case it is present then restore your infeasible database.
- After that transfer the mailbox to a healthy Exchange Server through ‘Move Mailbox' features in Administrator tool.
- Then execute ESEUTIL /P against the damaged database and check database for consistency by using the ESEUTIL /K command.
