Article ID: 810198
Article Last Modified on 2/27/2007
APPLIES TO
- Microsoft Exchange 2000 Enterprise Server
- Microsoft Exchange 2000 Server Standard Edition
SUMMARY
This article discusses the common causes of and resolutions to Exchange 2000 Information Store database corruption that is indicated by Event ID 454.
You may see the following event in the Application log of the Event Viewer:
Date: date Source: ESE Time: time Category: Logging/Recovery Type: Error Event ID: 454 User: N/A Computer: Servername Description: Information Store (976) Database recovery/restore failed with unexpected error Error Number.
Error Number is an error code that indicates the source of the problem.
Event ID 454 is a generic event that indicates a problem either with a restore operation or with the recovery of an Exchange 2000 Information Store database. Generally, Event ID 454 means that Exchange 2000 has determined that:
- Files in the database's running set are missing.
-or-
- Files in the database's running set have been replaced with different versions.
_or_
- Files in the database's running set are corrupted.
The error number in the Event Description indicates what the specific problem is. This article lists some of the most frequent causes and the corresponding resolutions for this event. The causes are organized by the error number that you find in the Description section of Event ID 454.
MORE INFORMATION
Description: Information Store (976) Database recovery/restore failed with unexpected error - 1216
Error - 1216 (hexadecimal 0xFFFFFB40) corresponds to error JET_errAttachedDatabaseMismatchwith the following definition:
An outstanding database attachment has been detected at the start or end of recovery, but the database is missing or does not match the attachment information.
The common causes and resolutions for this error are:
- Cause 1: This problem may occur if the Exchange 2000 Extensible Storage Engine (ESE) tries to bring all the databases in a storage group into a consistent state during the recovery process. To do this, the ESE keeps track of all the databases in the log files for the storage group. If a database is missing, the ESE returns error 1216 and does not start the storage group.
Resolution 1: To resolve this problem, either locate the missing databases and move them to the appropriate folders, or restore the missing databases from backup. For additional information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:264228 XADM: Storage Group Does Not Mount with -1216
- Cause 2: This problem may occur if other files in the running set of the database (such as transaction logs) are missing or have been replaced with different versions. When this error occurs, Exchange 2000 aborts the "soft" recovery of the database before it makes any changes that might prevent the re-integration of the missing or mismatched files with the data set.
Resolution 2: To resolve this problem, try to restore the missing database files or transaction logs. If these files are unavailable, you can use an option in the eseutil command to override the error and continue with the "soft" recovery of the database even though there are missing or mismatched files. For additional information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:296843 XADM: Error - 1216 Recovering an Exchange 2000 Database
- Cause 3: This problem may occur if you try to perform a restore operation to a recovery server and Exchange 2000 Information Store does not have access to Active Directory in the production environment. In this case, Information Store cannot locate the globally unique identifiers (GUIDs) for the associated databases.
Resolution 3: To work around this problem and replay the log files, you must copy all the transaction logs that you want to recover to a temporary restore folder that you defined during the restoration process. For additional information about this problem and detailed steps on how to resolve it, click the following article number to view the article in the Microsoft Knowledge Base:312635 XADM: Recovering Transaction Logs on a Recovery Server That Does Not Have Access to the Production Active Directory
Description: Information Store (1484) Database recovery/restore failed with unexpected error -552.
Error - 552 (hexadecimal 0xFFFFFDD8) corresponds to error JET_errDatabasePatchFileMismatchwith the following definition:
Patch file is not generated from this backup.
- Cause: This problem may occur if Exchange 2000 automatically generates patch files that use the same file name as the database that has a .pat file name extension. When the restore process on an online backup is completed, the patch files are written from the backup media into a single folder (that the user specified) on the hard disk. If the Exchange 2000 databases do not have unique names in the storage group, only one patch file is created on the hard disk, and the other patch files are overwritten.
Because only one patch file is available to restore multiple databases, the restore process is unsuccessful.
Resolution: To resolve this problem, make sure that multiple Exchange 2000 databases that reside in a single storage group have unique names, even if they are contained in different folders on the hard disk. Alternatively, if you are using Exchange 2000 Server Service Pack 1 (SP1), upgrade to Exchange 2000 Server Service Pack 2 (SP2) or later. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:311441 XADM: Uniquely Name Multiple Databases in Single Storage Group
Description: Information Store (976) Database recovery/restore failed with unexpected error - 2204
Error - 2204 corresponds to error JET_errSLVStreamingFileMissingwith the following definition:
Cannot find streaming file associated with this database.
- Cause: This problem may occur if the streaming file has been moved to another location by another process, for example, by an antivirus program.
Resolution: To resolve this problem, try to locate the missing .stm file or restore it from backup. If you are running an antivirus program, make sure , that the file has not been moved to the quarantine folder by the antivirus program. If the file was moved, move it back to the original location, and then reconfigure the antivirus program so that it does not scan the Exchange 2000-related folders.
Description: Information Store (2184) Database recovery/restore failed with unexpected error -501
Error -501 (hexadecimal 0xFFFFFE0B) corresponds to error JET_errLogFileCorrupt with the following definition:
Log file is corrupt.
- Cause: This problem may occur if a log file has become corrupted.
- Resolution:To resolve this problem:
- If the database files are consistent, move all the log files (.log) out of the Exchsrvr\Mdbdata folder and then mount the stores.
- If the database files are inconsistent, restore the database files from backup. If a valid backup is not available, repair the databases by using the eseutil /p command.
For additional information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:
301438 You cannot mount a database because there is a corrupted transaction log in Exchange 2000
To work around this behavior and replay the transaction logs, copy all the transaction logs that you want to recover to the temporary restore folder that you defined in the restoration process. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:312635 XADM: Recovering Transaction Logs on a Recovery Server That Does Not Have Access to the Production Active Directory
REFERENCES
Other error codes may be listed in the Description section of Event ID 454. For additional information about the error codes in Event ID 454, click the following article numbers to view the articles in the Microsoft Knowledge Base:
266361 XADM: Extensible Storage Engine 98 Error Codes 0 to -1048
Additional query words: IS information store
Keywords: KB810198
