|Message:||%1 (%2) %3Database recovery failed with error %4 because it encountered references to a database, ‘%5’, which is no longer present. The database was not brought to a Clean Shutdown state before it was removed (or possibly moved or renamed). The database engine will not permit recovery to complete for this instance until the missing database is re-instated. If the database is truly no longer available and no longer required, procedures for recovering from this error are available in the Microsoft Knowledge Base or by following the “more information” link at the bottom of this message.|
Database recovery failed because it encountered references to a database that is no longer present. The database was not in a consistent state before it was removed (or possibly moved or renamed). You may experience the following symptoms:
There is an error -1216 in the Description section of the event that states: Database recovery failed with error -1216 because it encountered references to a database path\database name that is no longer present. The database was not brought to a consistent state before it was removed (or possibly moved or renamed). The database engine will not allow recovery to complete for this instance until the missing database is reinstated.
If the database is truly no longer available and no longer required, contact Microsoft Product Support Services for additional instructions about what must be done in order to enable recovery to continue without this database.
This behavior occurs because the Extensible Storage Engine (ESE) tries to bring all databases in a storage group to a consistent state during recovery. To accomplish this, ESE keeps track of all databases in the log files for the storage group. If a database is missing, ESE returns error -1216 and does not start the storage group. Error -1216 is equivalent to Jet_errAttachedDatabaseMismatch. Error -1216 indicates that Exchange has determined that files in the running set of the database are missing or have been replaced with different versions. This error can also be represented in hexadecimal notation as 0xfffffb40. When this error occurs, Exchange exits the soft recovery of the database before it makes any changes to the database that might prevent the integration of the missing files that have the data set.
The location of the database(s) has been changed by using Exchange Management Console or ADSIEdit, or manually, and ESE thinks the database(s) are on one drive but they are actually on another drive. Only the .stm database file is missing or has been deleted.
To resolve this warning, do one or more of the following:
A -1216 error can also indicate missing transaction logs. You can force recovery to ignore the missing files by running Eseutil /R /I.
There is a second error -1222. This error may be seen in the Description section of event 494 and translates to a 0xfffffb3a error code, or Jet_errDatabaseSignInUse (a database with the same signature is in use). This can mean another copy of the same database is already running, or it can mean that the log files consider that the database is one drive, whereas it is on another drive, or that an attempt was made in ESM to move the database to another drive, but the move was not completed. If Error -1222 is received, you may be able to run Eseutil /R /I, or you may have to restore from an online backup.
If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.