Unable to Mount Database (hr=0x80004005, ec=1108)
Sometimes while working on MS Exchange 2010, a user might delete some log files that have not been written to the respective database yet. This kind of situations can give rise to the serious errors in Exchange Server. One such error message is unable to mount mailbox database in Exchange 2013, 2010 and 2007. This error mainly occurs when a user tries to mount the database.
In additional, the another possible reason behind this error can be a dirty shutdown of the system. Whenever there is a dirty shutdown, a user may lose access to important log files that further give rise to corruption in the Exchange database. All these types of situations make it difficult for a user to access the database files and a user needs to suffer from a data loss. Thus, it is really important for any user to fix unable to mount database (hr=0x80004005, ec=1108) error message to get access back to the database without any problem.
Type of Error Message:
While mounting database to Exchange Server 2013, 2010 and 2007, a user may encounter following error message:
Why Unable to Mount Mailbox Database in Exchange Error Occur?
There can be various possible reasons behind this error in Exchange and all of them are discussed below:
- One of the major cause behind this error is abnormal termination of an application or a dirty Shutdown.
- Deletion of the log files that has not been written to the database yet.
- Corruption in the database of Exchange Server 2013, 2010, 2007.
To overcome all these situations there are some resolution steps that a user must follow before directly jumping to the recovery of Exchange database or log files.
Resolution 1: Check and Repair the Database
If corruption in the database is the reason behind this error, then a user first need to check the database and then take it out of the dirty shutdown state. Thus, to repair the data run the following commands: eseutil /p
"C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database\Mailbox Database12.edb"
After executing the command, re-run the database again and check the output state. If it is a Clean Shutdown, then a user can mount the database. However, if the mounting process does not go well, they check the database logs.
Resolution 2: Check & Repair the Database Logs
While checking the Exchange Logs do not forget to specify E00 as the starting sequence for the logs and run the following: eseutil /ml
"C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database\E00"
It will display the list of all logs with their state, a user may receive an error. However, if there is no problem with log files, then a user need to proceed further to resolve this error.
Methods to Fix Unable to Mount Database in Exchange Issue
In order to resolve failed to mount mailbox database in Exchange 2013, 2010 and 2007 error, one can follow any of the three methods, including professional solution are discussed below:
Approach 1: Execute the Command Setup /PrepareAD
A user can run the Setup /Prepare AD command from the CD of Exchange Server to ready the Active Directory service for Exchange Server 2010.This command will repair and recover the Exchange Server configuration in Active Directories automatically. To do the same, follow the steps given below:
In Exchange Server 2010
- To begin, start the Exchange Server 2010 Help
- After that, click on the Contents tab and then click on Deployment >> New Installation >> Preparing to Deploy Exchange 2010,
- Now, click on How to Prepare Active Directory and Domains
Approach 2: Use Domain Controller to add the Exchange Servers group to the "Manage auditing and security log" policy
In order to add Exchange Servers group into the Manage auditing and security log policy, follow the steps listed below:
- First of all, Log on to the domain controller using account having administrative rights
- After that, navigate to Start >> Administrative Tools >> Domain Controller Security Policy
- Now, the Microsoft Management Console (MMC) snap-in the Default Domain Controller Security Setting and expand the Local Policies
- After this, click on the User Rights Assignment and open Manage auditing and security log from the right pane
- Now, in the Manage auditing and security log Properties dialog box, click on the Add User or Group option and type DomainNameExchange Servers in the User and group names box, then click OK >> OK option
- Then, you can exit the Default Domain Controller Security Settings MMC snap-in, and then wait until the security setting propagates across the domain controllers in the domain.
- After that, you can restart the Microsoft Exchange Information Store service
Approach 3: Using a Professional Tool
The two manual approaches discussed above are not foolproof solutions. There are chances that a user might unable to mount mailbox database in Exchange 2013, 2010 and 2007. Thus, in order to have a guaranteed solution, it is advised to use SysTools Exchange Recovery Tool to remove all type of corruption from Exchange database file. It is the tool that repair Exchange mailbox database without any loss of data. The software has the ability to recover damaged, inaccessible and password protected EDB file and export it to PST file format without any limitation.
The Bottom Line
Inaccessible data in Exchange Mailbox is a big problem for any Exchange Server user. As a user encounter many errors while using Exchange Server 2013, 2010 and 2007 and one such is unable to mount the database. (hr=0x80004005, ec=1011) that is important to resolve. Thus, after understanding the reasons behind the occurrence of this “failed to mount the database error” various solutions are also suggested. A user can refer them easily based on the cause of the error. Moreover, in order to get access back the Exchange mailbox data without any data loss, a third-party tool is also suggested that proves to be a perfect and reliable solution.
0 comments:
Post a Comment