Tips to Fix Bad Page Link Error - 327 in MS Exchange Server

Corruption issue in Exchange Server database files is fairly common occurrence. Many factors, like unexpected system shutdown, malicious virus, human errors, power outage, etc. Corruption of Exchange Server may fall you into a grave problems. Loss of Exchange Server data is one of the symptoms that are observed after the corruption of Exchange database. A latest backup helps you to gain access of data again which you have lost due to corruption. In case of unavailable backup, you have an option of a third party tool.

Sometimes, it happen Information Store service remains unstopped when Exchange Server 2000 or Exchange Server 2003 is in use. Along with failure to start Information Store service, it throws an error message that looks exactly same as given below:

“1067 The information store terminated abnormally.”

Moreover, the below stated event ID is seen in the application log of Windows Event Viewer:

“Date:      date        Source:   ESE

Time:      time        Category: (12)

Type:      Error       Event ID: 447

User:      N/A

Computer:  Servername

Description:

Information Store (nnnn) A bad page link (error -327) has been detected in a

B-Tree (ObjectId: 19, PgnoRoot: 113) of database E:\Program

Files\Exchsrvr\mdbdata\priv1.edb (3440582 => 3443648, 3443232).”

Cause:

Hardware failure or antivirus scanning of the database file directory is the responsible reason for the occurrence of above error message. Event ID 447 recognizes that the structure of the logical database has become corrupt. Logical database get corrupt for one or more of the following reasons:

·         Disk caching has not committed transactions to the hard disk and the server has stopped working.

·         Replay of wrong log files at a time of a restoration of database.

·         Bad hard disk controller in a server.

·         Removal of database log files that were partially committed to the database.

Solution:

In order to overcome this problem, try to restore the database from an online backup. If no backup has been maintained by you, then the only option left for you is to repair the corrupt or damaged Information Store database. Below are the steps to repair the information store database:

1. Open the Information store service if it is not already started.
2. Open Exchange System Manager, and then dismount the corrupt private database.
3. Execute the eseutil/p command for the dismount database file.
4. Backup the original database files.
5. Open Exchange System Manager, and then mount the Exchange Server database.
6. Dismount the database.
7. Execute isinteg -s servername -fix -test alltests command at the command prompt for the problematic database.
8. Open Exchange System Manager and then mount the database.

It might be possible that Exchange Server database remains not repaired, even after performing the above steps. So, in such situation it is advised for you to opt for third party Exchange Server Recovery software. A lots of software have been introduced that performs the job of Exchange Recovery with much ease and instantly. After the use of any of such product, data of all the Exchange Server objects, such as contacts, attachments, appointments, journal, tasks, events, etc gets recovered. A third party tool is an apt solution for inaccessibility of data. A help file comes along with the software that guides you how to perform recovery with these tools.