Thursday, August 12, 2010

Unable to mount MS Exchange Server 2007 could be corrupt

Are you unable to mount EDB (Exchange Database) database file on the MS Exchange Server 2007 system that is being used in your organization? If yes, then there is a very prominent possibility that the EDB file is corrupt thereby disabling you from mounting it. In such cases, you should try to find out the exact cause of corruption and try to eradicate that issue. In case, nothing is succeeding then you should use a professional Exchange repair software to recover the trapped data.
Consider a similar situation in which you are unable to mount the database on MS Exchange Server 2007. The following error message is displayed:

“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 error log the following event is logged:

“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 (0x00000002): "The system cannot find the file specified." The move file operation will fail with error -1811 (0xfffff8ed).”


You may have run the eseutil /p command on the damaged databases. This problem has occurred because the transaction log files were not removed during the process.


First of all, you should check whether eseutil was run on this system at all or not by performing the following steps:
1.Click Start | Run.
2.Enter 'CMD' in the 'Run' box and press 'Enter' key. The Command Prompt window will be displayed.
3.Enter the following command:
4.c:\program files\exchsrvr\bin\eseutil /mh "c:\program files\exchsrvr\mdbdata\name of Exchange database.edb"
5.Check the repair count field. If it is 0, then the eseutil /p command was not run. For a non-zero count, eseutil /p command was run on the database.

Now, you can transfer the transaction log files to another folder if the database is in a clean shutdown state. To check this condition, you should perform the following steps:

1.Click Start | Run and enter 'cmd' in the 'Open' box and click OK.
2.To check the private information store, enter the following command in the Command Prompt:
3.c:\program files\exchsrvr\bin>eseutil /mh "drive:\program files\exchsrvr\mdbdata\priv1.edb"
4.To check the public information store, enter the following command in the Command Prompt:
5.c:\program files\exchsrvr\bin>eseutil /mh "drive:\program files\exchsrvr\mdbdata\pub1.edb"
6.Analyze the consistency check results. If the database is consistent, then all the transaction log files are moved to the information store.
7.Transfer all the log files from the directories to a backup folder.
8.Now try to mount the database. It should run fine now.

In the event of still unable to mount the database, the only way of resolving this problem is to use a third-party MS Exchange repair software. These tools are highly interactive in nature that do not damage the EDB files while scanning them.

The best Exchange repair software among all the available tools is Stellar Phoenix Exchange Server Recovery that repairs corrupted EDB files integrated in MS Exchange Server 5.5, 2000, 2003, and 2007. Compatible with Windows 7, Vista, Server 2003, XP, and 2000, this Exchange Server repair tool is able to extract individual user mailbox in the form of separated PST files.

For more visit at:

No comments:

Post a Comment