Thursday, 25 April 2013
4/25/2013 02:50:00 am 0

How to resolve ESE event ID 467 in Exchange?

Exchange database consists of two main components i.e. Information Store and the JET Database Engine. JET Database Engine tracks and maintain all the transaction processing. All database management tasks are handled by information store. It maintains the Exchange user mailbox data in private information store (Priv.edb) and public folders data in public information store (Pub.edb).  

Exchange Information Store is the key component of Exchange database; if it gets corrupt then Exchange server couldn't function properly and will generate several error messages whenever, user tries to access the Exchange mailbox data. ESE Event ID 467 is one of the common errors generated due to Exchange database corruption. 

ESE Event ID 467:
ESE Event ID 467 is generated due to Exchange store database corruption. Exchange Information Store services and JET engine will stop responding when this Event ID has occurs.

Cause: ESE Event ID 467 indicates logical corruption in the Exchange store database. It occurs when secondary index of a table in the Exchange store database gets corrupt or inconsistent. In such situation when you try to insert a record in the table, an index entry will be made that makes the corrupted page to be flushed but the index will not get flushed with the corresponding table. Thus, it generates inconsistency in the Exchange Information Store database.

First locate the corrupt database; you can easily view the location of the corrupted database from the Description section of the event.

Note: You may require installing the supported hot fix, if you cannot view this information about the corrupted database.

Once you have traced the corrupt database, follow these steps to fix the problem: 
1.First, Start Exchange System Manager
2. Dismount the corrupt database
3. Check database inconsistency by running eseutil /g command. 
If it is still showing database corruption then, repair the database using eseutil /p, then run Isinteg -fix. This will fix the page or database level corruption.
4. De-fragment the database by running eseutil /d command. Running (Eseutil /d) will help you to resolve logical corruption in Exchange database.
5. Once you have performing database fragmentation then, use ExMerge to rebuild, and mounting the Exchange database for putting it back into production.

If the problem still persists, delete the corrupt database and use your recent valid backup copy of database to restore it.

ISINTEG command is used to check the Exchange store database corruption related issues and ESEUTIL for dealing the problems with the database engine. Eseutil and Isinteg fail in several situations and can also lead to data loss situations because these utilities delete the corrupted page instead of actually repairing it. So also backup your database before running these commands. 

To overcome the limitations of the inbuilt Exchange Repair utilities, you need some powerful Exchange server recovery software that can perform efficient Exchange database repair without causing any kind of data loss.


Post a comment