Usually, the occurrence of logical corruption in MS Exchange database arises at the database level. An example of this specific type of database corruption is when the index entries refer to the missing value. It can also happen at the email application level causing damage to the Exchange Mailboxes, folders, messages, attachments as well.
Logical corruption usually occurs at the database engine or in the Information Store which results in serious destruction in Exchange Mailbox Data.
In such scenario of logical corruption, you may come across Exchange Server Error 327 which is also known as "JET_errBadPageLink" error on the screen. Along with the error, you may also come across the below mentioned error on the Window Application log:
"MSExchangeIS ((###)) The database engine found a bad page"
Such error of "bad page link" is due to server disk crash or may of cause of bug in Exchange Server. Another reason which causes the emergence of such error is when incorrect transaction log files is replayed after processing the database through the updated backup.
Troubleshoot Exchange Error 327 with Various Steps
Note: In some cases where the degree of corruption is too high, the above methods are most likely to fail and might cause more corruption and difficulty to recover data from EDB file. Therefore, it is recommended to use third party tool in order to mount EDB file recovery from errors without any difficulty.
Exchange Files Recovery, a highly technical application which is designed to eliminate the corruption from the Exchange database. The software repairs the Exchange database from the damage or offline EDB files and allows restoring it to Outlook PST as well as various other file formats like EDB, EML or MSG.
Exchange Recovery Software allows the recovery of database while retaining the hierarchy and accuracy of the EDB files to a user-specified location. Download free demo to know how to recover EDB to PST and various advance features of the tool.