Export (0) Print
Expand All
5 out of 7 rated this helpful - Rate this topic

Reference for Common Eseutil Errors

 

Topic Last Modified: 2006-08-17

This section covers common Extensible Storage Engine (ESE) errors encountered when running Eseutil on your information store database files, transaction log files, and streaming files.

The table below describes some of the common database errors encountered when running Eseutil.

 

Error number JET Error Error Description

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 -501 (0xfffffe0b)

JET_errLogFileCorrupt

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)

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 -514 (0xfffffdfe)

JET_errBadLogVersion

This error occurs when trying to replay a log file that was generated with a different version of Exchange. This error may occur after upgrading to a major version of Exchange, and occasionally may happen after a service pack or hotfix upgrade that alters the database schema or internals. Service packs that can trigger this error include Exchange 2000 Server Service Pack 1 (SP1) or Service Pack 2 (SP2), Exchange Server 2003 SP1, and Exchange Server 5.5 Service Pack 4 (SP4).

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 -519 (0xfffffdf9)

JET_errLogSequenceEnd

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 one. Database behavior, after this limit is reached, varies by Exchange version. 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 -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 -531 (0xfffffded)

JET_errBadDbSignature

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, either 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)

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 -533 (0xfffffdeb)

JET_errCheckpointCorrupt

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

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 -540 (0xfffffde4)

JET_errDatabaseStreamingFileMismatch

For more information, see Error -537.

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.

noteNote:
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)

JET_errSoftRecoveryOnBackupDatabase

This error indicates that in place of 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 crash. 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)

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 -549 (0xfffffddb)

JET_errStreamingDataNotLogged

This error occurs when circular logging is enabled and data placed in the streaming database (.stm file) is not logged. Circular logging causes log files to be deleted soon after their data has been written to the database file. This reduces disk space requirements for transaction logging, but also prevents rolling the database forward from a backup. By default, circular logging is disabled, and the online backup process is relied on to remove excess transaction logs that are no longer required for rolling the database forward. If you change circular logging settings, you should immediately perform a full backup.

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

JET_errConsistentTimeMismatch

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. For more information about resolving the error for Exchange Server 2000, see the Microsoft Knowledge base article 296843 "How to recover an Exchange 2000 Server database after error -1216."

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 -1216 (0xfffffb40

JET_errAttachedDatabaseMismatch

This error is closely related to error -551 (JET_errConsistentTimeMismatch). It typically occurs after a simultaneous crash of all databases in a storage group if one of the databases is no longer available (for example, because its disk has been destroyed). For more information about resolving the error for Exchange 2000 Server, see the Microsoft Knowledge base article 296843 "How to recover an Exchange 2000 Server database after error -1216."

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."

Error -939586631 (Unknown

Error, Unknown Error)

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. If the issue persists, you can run Eseutil /P followed by Eseutil /D, and then try running Eseutil /CC again to recover the database. For more information about running Eseutil /CC, see How to Run Eseutil /C (Restore) in Different Scenarios.

For more information about these error codes, see

For more information about understanding Extensible Storage Engine (ESE) file types, see Extensible Storage Engine Files.

For more information, see the following topics in the Exchange Server Database Utility Guide:

 
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.