Reference for Common Eseutil Errors

Error -327 (0xfffffeb9)

JET_errBadPageLink

This error occurs when there is logical corruption in the database. Logical corruption can be caused by a bug in Exchange or by a hard disk crash. A crash can cause the error if write ordering of pages from cache was not preserved, and therefore only some pages from a transaction were updated while other pages were left as older versions.

Error -510 (0xfffffe02)

JET_errLogWriteFail

This error indicates that Exchange was unable to write to the current log file. The log disk may be full, a hardware error may have made the disk inaccessible or another process may have locked the log file.

Error -515 (0xfffffdfd)

JET_errInvalidLogSequence

This error indicates that a log file is missing or does not match the other log files. This can happen if the log signature does not match, if the creation time does not dovetail with other logs in the sequence or if another problem is detected which indicates this log was not part of the original sequence. This error is seen most often because a log file is missing. It may also be seen in circumstances where multiple restorations of a database have left you with multiple log streams for that database, and you have tried to blend the log streams.

Error -530 (0xfffffdee)

JET_errBadLogSignature

This error indicates a signature mismatch. The signature is actually "good" but it does not match other log files in the sequence or does not match the log signature recorded in the database. This could be because log files from different sequences have been found or that a database has crashed and the logs needed to recover it are no longer present.

Error -532 (0xfffffdec)

JET_errBadCheckpointSignature

This error indicates that the checkpoint file does not match the transaction log files. Removing the checkpoint file will correct this error. It will also cause Exchange to re-scan every transaction log to determine whether it is needed for recovery. If there are thousands of log files, this may take several minutes or more.

Error -537 (0xfffffde7)

JET_errBadSLVSignature

This error indicates that the current .edb file and .stm file do not match each other. An Exchange 2000 Server database or Exchange Server 2003 database consists of two files--the .edb MAPI database file and the .stm streaming database file. These files must be kept synchronized with each other, and they cannot be used with other databases.

Error -543 (0xfffffde1)

JET_errRequiredLogFilesMissing

This error indicates that log files are missing. An Exchange database that has been shut down correctly is in a Clean Shutdown space and has detached from its log files. The database is now independent of the log files. All existing log files could be deleted and the database could be restarted with a new or different set of log files.

If a database has not been shut down correctly, it is still attached to one or more of the log files. These log files are required to bring the database to a consistent state. If these log files cannot be made available, the database must be restored from backup or repaired before it can be started again.

Error -548 (0xfffffddc)

JET_errLogSequenceEndDatabasesConsistent

This error may accompany error -519, and indicates that no more transaction log files can be generated in this sequence, but databases are all in Clean Shutdown mode. This means it is safe to remove transaction log files and reset the log sequence. For more information about resolving this error for Exchange 2000 and Exchange 2003, see the Microsoft Knowledge Base article 830408, "Exchange database stores remain mounted although all transaction logs that are available to a storage group have been used."

Error -550 (0xfffffdda)

JET_errDatabaseInconsistent

This error will occur if transaction log files are missing or not all data from the log files could be applied to the database. If a database is unexpectedly stopped, it will be in Dirty Shutdown state. (The state of a database can be viewed by reading the database header while the database is stopped. For more information, see section on Eseutil /M File Dump Mode).

A database in Dirty Shutdown state is still attached to its transaction log files and must have required log files applied to it before it can be started. To correct this error, you must apply all required log files, restore the database, or repair the database.

Error -552 (0xfffffdd8)

JET_errDatabasePatchFileMismatch

This error can occur in versions of Exchange prior to Exchange 2000 Server Service Pack 2 (SP2) after restoring from a streaming online backup. The patch file is a file used in transaction log replay for older versions of Exchange. Optimizations in Service Pack 2 for Exchange 2000 allow hard recovery to proceed without patch data.

Error -1206

JET_errDatabaseCorrupted

This is a generic error and does not necessarily indicate a severe problem. The error will trigger at the end of an integrity check where problems of mild to medium severity have been found. Scan the <database>.integ.raw file for the word ERROR to get detailed information about issues found in the database.

For more information, see the Events & Errors Message Center.

For more information on resolving the error for Exchange 2000 Server Standard Edition, see Microsoft Knowledge Base article, 313704 "XADM: Running an Integrity Check on the Srs.EDB Database Always Returns a JET_errDatabaseCorrupted Error Message."