Exchange Server databases have two basic files, EDB and STM. As its supports transaction logging, uncommitted set of transactions are stored in log files. Users’ mail boxes are stored in EDB files. So when Exchange Server database corrupts, EDB Recovery is basically focused for extracting user mailboxes from EDB files. However, one of the symptoms that Exchange database is corrupt is that it will fail to mount. In addition, it will mark an event in application log like:

 

Event Type: Error
Event Source: ESE
Event Category: General
Event ID: 486
Description: Information Store (3932) First Storage Group: An attempt to move the file “E:\Program Files\Exchsrvr\mdbdata\E00.log” to “E:\Program Files\Exchsrvr\mdbdata\E000080A.log” failed with system error 2 (0×00000002): “The system cannot find the file specified.” The move file operation will fail with error -1811 (0xfffff8ed).

Also, an error message is encountered about internal processing errors. Other than Exchange database corruption, above log may also create while these issues:

  • Application log may record this event due to un-removed log files after running eseutil/p repair command on damaged Exchange database
  • It may also occur if log file has been deleted by antivirus program. Also if log file is quarantined by such programs, database may fail to mount
  • Incorrect usage of eseutil /r three-character logfile base name command may also create the same issue. It particularly happens if logfile base name is incorrectly specified

Solution

  • If un-removed log files are the issue after using esuetil/p command, we need to first check database consistency. If it is correct, we can move these log files to some other folder. However if database is reported as damaged, we can try committing all log files to the database. If problem persists, users are required to apply Exchange Server Repair solutions.
  • Antivirus program is not recommended to scan Exchange Server directories. So it should be excluded from file level scanning. This can even corrupt the database.
  • We need to correctly use eseutil /r command and logfile base name.

 

Exchange Server Recovery
Third party Exchange Server Repair solutions are applicable if user has no valid backup. Exchange Repair Software can scan damaged Exchange database and extract all user mailboxes.