Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1, Exchange Server 2007
Topic Last Modified: 2007-02-19

This topic covers common Extensible Storage Engine (ESE) database errors that you might encounter when running Eseutil on Microsoft Exchange database files and transaction log files in a storage group. Formerly known as JET, ESE is a method that defines a low-level API to the underlying database structures in Exchange Server.

Error Codes

Table 1 describes some of the common database errors encountered when running Eseutil.

Table 1   Common database errors when running Eseutil

Error number JET error Error description

Error -327 (0xfffffeb9)


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 failure. A failure can cause the error if the write ordering of pages from the cache was not preserved, and therefore only some pages from a transaction were updated while other pages were left as older versions.

Error -501 (0xfffffe0b)


This error indicates physical damage to a transaction log file. It is similar in its causes and effects to an error -1018 in a database file. You cannot repair or recover a log file after this error occurs.

Error -510 (0xfffffe02)


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)


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 fit with other logs in the sequence, or if another problem is detected that 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 -519 (0xfffffdf9)


Exchange Server 2003 and earlier versions support log file sequences of up to 1,000,000 log files per storage group before the log sequence must be reset to 1. Database behavior, after this limit is reached, varies by Exchange version.

Error -530 (0xfffffdee)


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 failed and the logs needed to recover it are no longer present.

Error -531 (0xfffffded)


This error is similar to error -530. Both databases and log files have signatures that identify and match them to each other. It is not necessary in all cases that the signatures match, but when a signature mismatch affects recovery, error -531, -530, or both will be seen. In some cases, recovery can complete successfully after error -531, but its presence indicates that transaction log data was not able to be applied to the database.

Error -532 (0xfffffdec)


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 scan every transaction log again to determine whether it is needed for recovery. If there are thousands of log files, this may take several minutes or more.

Error -533 (0xfffffdeb)


This error indicates that a corrupt checkpoint file has been deleted. In most versions of Exchange, a corrupt checkpoint file will be deleted and re-created automatically. A corrupt checkpoint file may be deleted because it cannot be used.

Error -543 (0xfffffde1)


This error indicates that log files are missing. An Exchange database that has been shut down correctly is in a clean shutdown state 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.

Deleting log files for a clean shutdown database will affect the validity and roll forward capabilities of previous backups.

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 -544 (0xfffffde0)


This error indicates that instead of a hard recovery, a soft recovery was performed on the database. If a database is restored from a streaming online backup, it is in a special state that requires hard recovery, as contrasted to soft recovery, which runs after an ordinary database failure. Hard recovery is run by triggering transaction log replay within the backup application or by running Eseutil /CC after database and transaction log files have been restored. For more information about running hard recovery, see Eseutil /C Restore Mode.

Error -548 (0xfffffddc)


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 a clean shutdown state. This means that it is safe to remove transaction log files and reset the log sequence.

Error -550 (0xfffffdda)


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 a 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 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 -551 (0xfffffdd9)


This error is closely related to error -1216 (JET_errAttachedDatabaseMismatch). It is typically caused by restoring raw copies of one database's files while other databases in the storage group are in a dirty shutdown state.

Error -1206


This is a generic error and does not necessarily indicate a severe problem. The error will be triggered 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 and Errors Message Center.

Error -1216 (0xfffffb40)


This error is closely related to error -551 (JET_errConsistentTimeMismatch). It typically occurs after a simultaneous failure of all databases in a storage group if one of the databases is no longer available (for example, because its disk has been destroyed).

Error -939586631 (Unknown


Unknown Error

This error occurs when you try to run Eseutil /CC with an incorrect path to the Restore.env file. The mailbox store will fail to mount as a result of this error. You can resolve the issue by running Eseutil /CC with the correct path of the Restore.env file. For more information about running Eseutil /CC, see How to Run Eseutil /C (Restore). If the issue persists, the database might need to be restored or repaired.

For More Information