Event ID : 454 , 494

Issue : Hard page faults on exchange database, database can be down or can go down.

Event Source : ESE

Cause :
This behavior occurs because the Extensible Storage Engine (ESE) attempts 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 the error -1216, and does not start the storage group.
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.
• Files in the database's running set have been replaced with different versions.
• Files in the database's running set are corrupted.

Description : Information Store (976) Database recovery/restore failed with unexpected error Error Number -1216.

Action Required :

1. To resolve this problem, either locate the missing databases and move them to the appropriate folders, or restore the missing databases from backup.
2. If the missing database was deleted or lost, restore the missing database from a backup. While you are restoring this database, you can mount and access the other databases in the storage group by completing the following steps:

• Run eseutil /r Log Base Name /I. This allows ESE to take the databases that are present to a consistent state while ignoring the missing databases. After you run this command, any databases that are not present will require restoring from backup. You can specify the location of the log files with the /l option and the location of system files with /s option.
• Mount the databases in the storage group that are now present and consistent.
• Allow the users on the running database to access their mail.

Ref.Link :

1. http://support.microsoft.com/kb/810198
2. http://support.microsoft.com/kb/823168