|Message:||process name (process id) %3The database engine lost one or more bad columns of data in one record. It is highly recommended that an application-level integrity check of the database be run to ensure application-level data integrity.|
After a database repair with Eseutil/p, some columns in the ESE database
appear corrupted for a particular record.
You will receive the following phrase in the event Description:
ESEUTIL (number) The database engine lost one or more bad columns of data in
one record. 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 502 has been known to occur during
the repair. The event indicates that the repair process found one, or more than
one, bad columns of data in a individual record and tried to repair the
column(s), but the repair of the column(s) was unsuccessful and the column or
colulmns were discarded.
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 use ExMerge
to get the data back into the new database. As an alternative, use Move Mailbox to move
the mailboxes to an alternative server. If hardware problems are the root cause
of the database damage, do not use ExMerge or Move Mailbox until the root cause
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.