| Event Id | 42 |
| Source | EDB |
| Description | 0MSExchangeIS ((###) ) The database engine found a bad page. |
| Event Information | This event indicates that the internal structure of the database has been compromised, as the databases internal references (pointers) are mis-aligned and/or corrupted. The server may become unusually slow, sluggish, or unresponsive.
CAUSE: This can result from replaying the incorrect transaction log files after a restore operation. A JET_errBadPageLink error, or "bad page link," indicates logical corruption, not physical corruption. RESOLUTION: To work around this problem, perform the following steps: 1) Restore the Exchange Server Database from most recent Full Online Backup: 2) Use the "Move Mailbox" feature in the Exchange Administrator program to move users from the corrupt Exchange Server to another. Recreate the priv.edb file on the original server, then move the users back to the original server. 3) Attempt to run EDBUTIL /D (Offline Defrag). 4) Attempt to run EDBUTIL /D /R (Repair) . |
| Reference Links | Event ID 42, The database engine found a bad page How to Recover from Information Store Corruption |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.