Toll Free: +1 888 900 4529
| 
Toll Free: +44 800 088 5522 
Toll Free: +1 888 900 4529
| Toll Free: +44 800 088 5522 ‘This blog contains the various causes and possible resolution of Jet error code 327 (JET_errBadPageLinks)“
Information Store (IS) of Exchange Server may get corrupted due to many different errors like Dirty Shutdown, Network Errors, Virus Attack, etc.
The speed of server falls down in case of the corruption in Information Store. You may also find problems in: –
You may also find many error codes indicating inconsistency in the Exchange Database.
Exchange Server uses transaction logs files to maintain the changes made in the Exchange Database.
These transaction log files are replied in the Event when a crash occurs to maintain the consistency in the Database. After the restore operation of Exchange database, sometime incorrect transaction log files are replayed. In such cases you will find an error message in the Event viewer.
In case of corruption in Exchange database, it is recommended to restore it from the updated backup copy of Exchange database. In case, if you don’t have an updated copy, then you have to repair it for that you can use ESEUTIL command.
Unmount the Exchange database and run the Powershell command Eseutil/P. After that, run the Eseutil/k command to check the consistency of database.
In this article, I have clarified the main reasons and possible solution of the Error code 327 (JET_errBadPageLink). For further assistance please comment.
