Know how to fix errors in MS Exchange server 2007

There are many circumstances in MS exchange server 2007 where you are unable to mount the exchange folder from edb files. There can be a number of reasons for this situation such as virus attack, file header corruption, unexpected system shutdown, human errors, oversized edb and many more. All of these reasons lead to inaccessibility of edb files as well can even direct you to severe data loss situations. There arises the need to go for edb recovery.

Consider a situation where you are trying to mount the database in Microsoft Exchange server 2007 but in the middle got an error message similar to this one:

“An internal processing error has occurred. Try restarting the Exchange System Manager or the Microsoft Exchange Information Store service or may be you are getting both messages”.

In case when the application log file is verified, the following error signature is observed:

“Event Type: Error
Event Source: Antivirus_Program_Name
Event Category: None
Event ID: 5
Description: The description for Event ID (5) in Source (Antivirus_Program_Name ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Virus Found! Virus name: W32.Netsky.P@mm!enc in File: E:\Program Files\Exchsrvr\Mailroot\vsi 1\Queue\NTFS_216f566e01c43c76000002af.EML by: Realtime Protection scan. Action: Clean failed: Quarantine failed: Access denied.”

Cause:

  • Firstly, if the antivirus program has deleted the original transaction log file
  • Secondly, if you have used Eseutil/p command to repair the damaged databases but transaction log is not removed
  • Another reason can be the mismatching signature and LGeneration related to exchange log file

Solution:

After going through the error causes, you need to go for the following resolutions:

First of all, check the antivirus settings if they have been configured to scan the exchange server directories. If yes, then restore the transaction log file deleted by the antivirus program.

Make sure that the Eseutil command had been run on damaged database perfectly

In case of database corruption, you can contact with Microsoft Product Support Services (PSS) for its resolution. But if it does not work, then the best is to opt for Microsoft Exchange server edb repair tool that ensures you for complete recovery and restoration of the corrupted edb database.