Are you encountering problems while mounting a database on an Exchange Server? Usually, such issues occur when if an anti-virus program deletes the Exchange Server log file. Another prominent reason could be corruption in vital EDB files. In such situation, you should address the problem by adopting several Exchange Server recovery measures to repair the database and bring it to consistent state. If you fail to resolve the issues, you can perform recovery for Exchange Server database files by employing a professional recovery software.

Consider a scenario, wherein, you try to mount a database on a server that is running Microsoft Exchange Server, and instead receive the following error message:

“An internal processing error has occurred. Try restarting the Exchange System Manager or the Microsoft Exchange Information Store service, or both.
ID no: c1041724
Exchange System Manager”

Additionally, the following event is logged in the Application log:

Event Type: Error
Event Source: MSExchangeSA
Event Category: (14)
Event ID: 9175
Description: The MAPI call ‘OpenMsgStore’ failed with the following error: The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance. The MAPI provider failed. Microsoft Exchange Server Information Store ID no: 8004011d-0526-00000000


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).


The above error message can surface in the following conditions:

1. Error 1811 relates to JET_errFileNotFound. This issue may pop up in an Exchange log (E00.log)  file that has a mismatching signature and LGeneration. If E00.log file has a mismatching signature, the information store won’t mount even if the databases are consistent.
2. If an anti-virus program quarantines, deletes or interferes the current Exchange log file.


To perform Exchange recovery,  ensure the anti-virus is not configured to scan the Exchange Server directories. Check the log files of the anti-virus program to verify whether the Exchange log file was quarantined or deleted.

1. If quarantined, recover the Exchange log file by executing the following steps:

a) Recover the Log to folder which contains production files
b) Start MS Exchange Information Store Service. In case other Exchange log files are not missing, the database will mount. In case more log files are found to be missing, check the missing log files in the quarantine folder. If you cannot find the files, follow the next step.

2. If deleted, recover the Exchange log file by following these steps:

a) Move all the inconsistent databases to backup folder
b) In case, new E00.log file is made, move it to the backup folder. Also, move E00.chk and copy the existing files.
c)Rename last E00*.log file as E00.log
d) Restore database from backup.

If you do not have a backup, you must consider using third-party Exchange Server recovery software to bring EDB database files to consistent state.

Stellar Phoenix Mailbox Exchange Recovery extracts inaccessible data from corrupt .edb files and  is compatible with Exchange Server 5.5, 2000, 2003, and 2007. This Exchange recovery tool recovers all e-mail messages, notes, journals, tasks, contacts and other components.

Visit here to download stellar phoenix mailbox exchange recovery software: