The Information Store service repeatedly stops responding and event ID 467 is logged

The Microsoft Exchange Information Store service may repeatedly stop responding (hang). This symptom may occur up to several times a day. The following events may be recorded in the system event log:

• Event ID 7011
• Event ID 7031

The following event may also be recorded in the application event log:

• Event ID 467

Each of these event ID 467 errors is associated with one 1025 warning in the MSExchangeIS Public/Private Store that is generated at the same time. For example, you may receive a message that is similar to the following:

This issue may occur if a database page is corrupted. This may cause the Microsoft Joint Engine Technology (JET) database engine to stop responding.

To resolve this problem, perform an offline defragmentation of the database that contains the corrupted data. To do this, follow these steps:

1. Locate the Exchange computer that has the corrupted database.
   
   For additional information about how to determine which database is causing event ID 467, see the “More Information” section.
2. Start Exchange System Manager.
3. Dismount the database that is causing event ID 467.
   
   To do this, right-click the database, and then click Dismount Store.
4. To confirm the database corruption, run eseutil /g on the database that is causing event ID 467.
5. If the database indicates corruption, run eseutil /d to defragment the database.
6. Repeat step 4 to confirm whether the database is consistent.
   
   The Eseutil utility should display Integrity check successful.
7. In Exchange System Manager, right-click the database, and then click Mount Store.

Important This problem may occur when the Exchange computer’s disk subsystem is not functioning correctly. It is a good idea to run disk subsystem diagnostics to look for input/output (I/O) failures.

The event ID 467 that is described in the “Symptoms” section indicates that the secondary index is inconsistent with the corresponding table. Both the secondary index and the table are specified in the Description section of the event.

When a new record is inserted into the table and the corresponding index entry is inserted into the index, database inconsistency may occur when the data page is flushed to the database but the index is not flushed. This event creates an inconsistent state with the database that is known as a “lost flush.” For more information about an update that is available to determine which Exchange information store database is causing event ID 467, click the following article number to view the article in the Microsoft Knowledge Base:

For more information about how to perform an offline defragmentation, click the following article number to view the article in the Microsoft Knowledge Base: