While working with MS Exchange Server, you need to mount the database file to access the user mailbox folders. There are various users’ mailbox folders, which contains user mailbox items including emails, messages, attachments, notes, journal, tasks, etc. At times, you might fail to mount the exchange folder.There could be different reasons for these situations that can make the EDB (Exchange Database) go corrupt and inaccessible. Some of these reasons could be incorrect settings in the antivirus, database header corruption, improper system shutdown, mishandling of the database file etc. You should adopt particular measures to overcome this problem. However, if it is not possible then you should use a trusted and reliable Microsoft Exchange recovery software to do the needful.
You can experience a similar kind of problem in different versions of the MS Exchange Server. However, let us consider a situation in which you are unable to mount the database of MS Exchange Server 2007. In this case, you may 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”
In addition, when you check the Application Log you may view the following error signature:
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.”
There could be the following reasons for this Exchange Server issue:
- The Exchange log file may have a mismatching signature and LGeneration. If the log file has a mismatching signature, then the information store may not mount even if the EDB database is consistent.
- An antivirus program may have deleted or quarantined the original Exchange log file.
- The 'eseutil /p' utility is run on the affected databases and the transaction log files were not removed.
- If you run the following 'eseutil' command using an incorrect logfile base name, as displayed:
“eseutil /r three-character logfile base name”
To overcome each of the aforementioned reasons, you can perform the following measures to achieve Exchange Server recovery.
- For the first cause, you should contact Microsoft Product Support Services (PSS).
- For the second cause, you should check the settings of the antivirus and see if the log file is deleted or quarantined. If yes, then restore the file.
- For the third cause, you should check whether the 'eseutil' command was run on the affected database.
- For the last cause, you should use the correct parameter to run the 'eseutil' command.
If you are still unable to access the Exchange store, then you should use a professional Exchange recovery tool to repair and recover the damaged EDB file. Such Exchange recovery software’s ensure a complete recovery of the database file including all the items within. These Exchange recovery tools are very safe to use and do not damage the original EDB database file during the recovery. In addition, they recover the file items in their original format. Moreover, they are easy to use because of their interactive and rich GUI.