Logical Errors is also the Cause for Corruption in Exchange Server: Fall of Microsoft Exchange Server in severe bad condition is 50% due to errors, to show dependency of any free inbuilt utility is useless because Microsoft offers no inbuilt utility to detect logical corruption in Exchange database files. The fact remains that there is no specific indications to identify logical damage in Exchange database however you find content in EDB files get inaccessible and you are not in a grave acute data loss situation.
Situation: Just imagine that in your organization Exchange Server is running to access data from MS Exchange Server, but all of sudden you find following entries in Application Event Log:
Event ID: 42
Source: EDB
Type: Warning
Category: General
Description: MSExchangeIS ((###)) the database engine found a bad page.
The above mentioned entries in Application Event log clears that logical corruption is the real cause of damage to Exchange Server database files.
Cause for Error:
Once you restore the database and if you replay the wrong transaction log file, logical corruption in Exchange Server database likely to take place.
Due to JET_errBadPageLink errors logical corruption in Exchange Server database occurs
