How to Fix ''1067 The information store terminated abnormally.'' Error in Exchange Server

Damage in an Exchange Server generally occurs at three levels, i.e. ‘Page level’, ‘Database level’, and ‘Application level’. Page level problems are surfaced as a result of hardware, driver, or firmware issues. These problems may also trigger problems at the higher levels. However, database level and application level damage occurs primarily due to problems in the Exchange code or other third-party programs. All these problems may lead to logical corruption of the Exchange server databases. As a consequence, all your precious information present in the database becomes inaccessible. To overcome this problem, you need to go for Exchange recovery through a reliable third-party utility.

For a better understanding of above issue, let us study a particular case of Exchange server database corruption. While using your Exchange Server 2000 or Exchange Server 2003 computer, you may receive the following error message on your screen:

''1067 The information store terminated abnormally.''

Moreover, Event ID 447 is observed in the application log of Windows Event Viewer.

Ground of the problem:

Above error may be caused due to a hardware failure or due to scanning of database file directory by an antivirus program. From the details of Event ID, it is clear that the logical structure of the database has become corrupt or damaged. The possible reason responsible for this corruption include replaying invalid log files at the time of restoration of the database. Other reasons could be a defective hard disk controller or transactions were not successfully committed to the hard disk before the server stopped responding.


This problem can be easily resolved with the help of an online backup. In case the backup is unavailable, you can try to perform a hard repair using the ‘eseutil.exe/p’ command. After completing the hard repair, perform an offline defragmentation of the database by running the ‘eseutil/d’ command and then, execute the ‘Isinteg-fix’ command.

If the problem still persists, then it indicates that the database is severally corrupt or damaged. In such circumstances, you can try out Exchange Server Recovery with the help of a third party tool. Such tools help you safely recover all valuable user mailboxes in the Exchange server database file.

Using a professional third-party tool is a good approach to easily repair damaged Exchange server EDB files and restore various mailbox items, such as emails, contacts, appointments, etc. It is suggested to use a tool of a reputed company, because it would recover the data much faster than any other methods. Demo version can be downloaded from the Internet. 

No comments :

Post a Comment