Article ID: 156415
Article Last Modified on 10/28/2006
APPLIES TO
- Microsoft Exchange Server 4.0 Standard Edition
This article was previously published under Q156415
SYMPTOMS
When attempting to start the Information Store service it may fail with an error -327 recorded in the application log. The entry in the application log may look similar to the following:
This error will be preceded by another application log event by EDB (JET). The entry in the application log may look similar to the following:
CAUSE
The Microsoft Jet database engine may perform maintenance on pages of the database without verifying that these page links are indeed valid. This can cause pages of the database to become corrupt.
WORKAROUND
Repair the corruption and then obtain the hotfix mentioned below.
RESOLUTION
If a current, valid backup of the database is available before the corruption occurred, use the following steps to repair the corruption:
- Apply the fix described below. This fix will prevent the corruption from happening with the restored good database.
- Restore the database from backup.
- Restart the Information Store service.
If a backup is not available, use the following steps (in the order given) to repair the corruption in the database:
NOTE: This process may result in loss of data.
- Perform an offline backup of the server making sure to include the Mdbdata directory/directories.
- In the \Mdbdata folder that contains the damaged store, run the following utility to remove the damaged page(s) from the database:
EDBUTIL /d /r <db name>
where <db name> is the database name (for example, priv.edb).
- Run the following utility to repair any Information Store or database inconsistencies that may have occurred from removing the bad page:
ISINTEG -fix -dbname
Where -dbname is the database name (for example, -priv).
- Restart the Information Store service.
After repairing the database corruption, apply the fix described below to prevent this type of corruption from occurring again. The fix allows the Microsoft Jet database engine to test the validity of the page links before performing maintenance on them.
STATUS
Microsoft has confirmed this to be a problem in Microsoft Exchange version 4.0. This problem was corrected in the latest Microsoft Exchange 4.0 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K
Keywords: kbbug kbfix kbusage KB156415
