Resolving issues with Microsoft Exchange Server can be very annoying and time consuming. Since, you can’t afford to proceed without restoring Information Store, the heart and soul of Exchange Server. You must review the error codes and corresponding error logs to start the recovery process. Oftentimes, the Information store doesn’t mount which is a clear hint towards possible corruption in its database files. The corruption could be caused by many factors including sudden loss of power, running Exchange Server on faulty hardware, and more. In all such cases, you would be required to observe appropriate remedial measures including using third-party Exchange recovery software.
Consider a scenario, wherein, you may come across the following symptoms on your Microsoft Exchange 2000 computer:
‘1067 The information store terminated abnormally‘
During online defragmentation, the following event is generated 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).
or
Date: date Source: ESE
Time: time Category: Database Corruption
Type: Error Event ID: 447
User: N/A
Computer: Servername
Description:
Information Store (nnnn) A bad page link (error -338) has been detected in a
B-Tree (ObjectId: 70950, PgnoRoot: 157120) of database e:\Program
Files\excshsrvr\mdbdata\priv1.edb (157120 => 296404, 296403).
Cause
The above error message and Event IDs suggest that it is a case of corruption. The logical structure of the vital Exchange database files of information store could have become corrupted due to the following reasons:
- The Exchange Server could have stopped responding since few transactions were not committed to the hard disk by disk caching
- Presence of a defective hard disk controller
- Incorrect log files were replayed while restoring the database.
You might not get to know about the problem immediately as logical database corruption is not detected by the backup program. You will only notice it when you try to access the page which has the data stored on it.
Resolution
Execute the following Exchange Server Recovery steps:
- Restore the corrupt database from the online backup
- Or perform hard repair by using Eseutil.exe / p command
- Now perform online defragmentation on the affected database using Eseutil.exe / d command
- Use Isinteg -s servername -fix -test alltests command which rebuilds the information store databases and fixes errors
Please refer to this KB article for complete step-by-step guide: http://support.microsoft.com/kb/810190
If you are unable to address the issue by the above-mentioned methods, then you could seek a professional Exchange recovery software from a reputed organization.
This is a guest post. The author of this post is an internationally renowned technical writer, data recovery expert and active blogger. As a data recovery expert with over 5 year of experience, she is well aware of the various critical issues that many users face in Exchange Server. She has written many articles about Exchange Server recovery to overcome the problems and to help the users of Microsoft Exchange Server.
