|Message:||process name (process id) %3The database engine lost one page of bad data. It is highly recommended that an application-level integrity check of the database be run to ensure application-level data integrity.|
The database may have been repaired, which may result in
lost data. Although the Repair process attempts to validate all system tables
and indexes, any data that cannot be repaired is discarded. If the database
cannot be repaired, a run-time error occurs.
You will receive the following phrase in the event
ESEUTIL (number) The database engine lost one page of bad data. It is highly
recommended that an application-level integrity check of the database be run to
ensure application-level data integrity.
When a database is in an inconsistent condition and a
repair using Eseutil /p is performed on the database, an ESE Event ID 500 has
been known to occur during the repair. The event indicates that the repair
process found a bad page and attempted to repair it, but the repair of the page
was unsuccessful and the page was discarded. ESE Event ID 500 has been found to be a serious error which can be indicative of a damaged database
If the repair process is successful, run Isinteg -fix on
the database. Then use ExMerge to save the data to .pst files, create a
blank database and ExMerge the data back into the new database. As an
hardware problems are the root cause of the database damage, do not ExMerge or
move mailbox back until the root cause has been fixed.
If the repair process fails because the database is too
damaged even for a repair, then you must restore from Exchange-aware online
backup. If there is no valid backup available, check to find out if users
are storing their data locally in .pst files on their client machines. If
they are, create a new blank database and use the .pst files to recover as much
data as possible.