Event 467 when Information Store service stops responding

Whenever any information is entered into Exchange database, index entry gets updated. So when you insert a new record in Exchange database table, Exchange inserts the corresponding index entry into index. Now if due to any reason, the data page is keep on increasing but the corresponding index remains intact, database inconsistency might arise. This particular state of database is known as ‘lost flush’.

You might have observed that MS Exchange Information Store services stops responding at repeated intervals of time in a day. On viewing the application event log, you come across event ID 467 associated with a 1025 warning:

Warning 1025:

An error occurred on database “First Storage Group\Public Folder Store (server_name)”

Function name or description of problem: SLINK:: EcUpdate Error: 0xfffffa7a

You come across a similar warning each time when event 467 is logged in MSExchangeIS public or private store.

Reason for this issue

Event 467 conveys that secondary index is inconsistent with the associated table. The database page is corrupted and is causing JET engine to hang.

Resolution

In order to resolve this issue, you need to first locate the corrupted database, which is specified in the Description section of event occurred. After the affected database is detected, follow the given below steps:

1. Start Exchange System Manager and dismount the database causing the issue
2. Run eseutil /g command to confirm for database inconsistency
3. Run eseutil /d command to defragment and fix the corruption
4. Mount the database store

If still the issue persists, then go for deleting the database but make sure that you have an updated valid backup. Backups are not the only solution, so if you are not having backup then you should try result oriented Exchange database recovery software. These tools are capable of resolving any kind of error issues related to Exchange Server database. One of the benefits of using Exchange database recovery tool is you can access the users’ mailboxes directly with Outlook, as the software provides option to save the recovered mailboxes in individual PST files.

Comments are closed.