Exchange Server stores all your critical information such as emails, notes, calendar etc and helps you perform wide varieties of tasks. However, some Exchange users have reported problems in mounting Exchange database files on Exchange server 2007. Unable to mount MS Exchange Server 2007 issues could be a result of severe EDB corruption which have disabled you from mounting. For resolving this problem, you will have to find out the exact cause of this behavior.
Let us consider a practical scenario in which you are facing problems in mounting database on MS Exchange server and get 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 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).”
Unable to mount MS Exchange Server 2007 database problems generally occurs if you will run eseutil command on your damaged databases. Due to damaged databases, transaction log files gets removed during the running process and creates lots of problems for you.
How to fix Unable to mount MS Exchange Server 2007 database problems?
In order to sort out this problem you have to find out if eseutil command run properly on your system or not. For finding this, you have to perform the following steps:
- First of all click on Start and go to Run.
- Type cmd in the box and press ‘Enter’. It will display the command prompt.
- In the command prompt enter the below given command: c:\program files\exchsrvr\bin\eseutil /mh “c:\program files\exchsrvr\mdbdata\name of Exchange database.edb”
- After that check repair count field and if it is 0, eseutil/p command did not ran. In case you get the count as non-zero, get assured that eseutil/p command had run on database.
After this you can transfer all transaction log files into another folder if database is in a clean shutdown condition. If you are still unable to mount database, you have to go for commercial MySQL Repair Software for fixing this problem. The software efficiently repairs your corrupted edb files and fixes unable to mount MS Exchange Server 2007 problems with the help of its advanced scanning techniques.