Fix & Repair Error “Not Able to Mount Database Exchange 2013!”
Each and every change performed in the database of Exchange Server is noted in transaction log files. These files are very crucial for normal MS Exchange server functioning. So, if a log file is removed by a user due to any issue then it would not be written to related database which can then generate many issues. For example, “not able to mount database Exchange 2013”. Whenever user attempts to mount the database, he/she could come across with an error “unable to mount database (hr=0x80004005, ec=1108)”.
Apart from this, there are other different errors too which can cause “not able to mount database exchange 2013” issue. One such reason is the sudden shutdown of the system. And there are possibilities that a user could lose the accessibility of important log files and leads to Exchange 2013 database corruption. All these circumstances creates a trouble in the Exchange 2013 database. Therefore, it becomes very essential task for a user to resolve the error: “Exchange 2013 Database won’t mount!” And to overcome the issue, multiple methods have been discussed in the blog which can help to discard the problem.
Common Error Message:
Below are some of the common error messages that occur when a user tries to mount database Exchange 2013:
Reason Behind “Exchange 2013 Database won’t mounting (hr=0x80004005, ec=1108)”
There could be several possible factors behind this error generating in Exchange and all of them are mentioned in the next section:
- The most common reason is the inappropriate system shutdown i.e. Exchange database dirty shutdown or an application.
- Log file deletion before that has been written to the database, this thing can also generate an error.
- Microsoft Exchange Server database corruption.
Methods to Fix, Repair Not Able to Mount Database Exchange 2013
If you are looking a way to resolve unable to mound Exchange 2013 database then no need to think of it anymore. Because in this segment we are going to highlight four methods to fix and repair the issue.
Method 1. Check & Repair database of MS Exchange
One should check the Exchange database if the cause of error is corruption. After that, take it out from dirty shutdown situation. Now, in order to fix the issue, execute the following command: eseus /p. This command help you out in repairing the corrupted Exchange 2013 database which is stored in the following location of the system:
“C:\Program Files\Microsoft Exchange Server\V14\Mailbox Database\Mailbox Database10.edb”
Once the command gets executed, try to run the database again and confirm the output situation. And if the shutdown performed in a clean state then a user can mount the Exchange 2013 database. However, still if there are some issues when mounting the data such as error messages are popping up again and again “Exchange 2013 missing log files”, then cross-check the database logs.
Method 2. Fix & Repair Exchange 2013 Log Files
If Exchange EDB is great, if there is no single issue in EDB file, then you need to check Exchange log file. Additionally, when verifying the log file, always mention E00 as the starting log sequence and perform the execution by running this command: eseus /ml. By making use of the command there are chances that one can repair Exchange 2013 log file.
C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database\E00”
After above command execution, all the logs will listed along with their state. Also, it is possible that an error can be received by a user. But, if there is no issue with Exchange log file then follow Method 3 to resolve an error.
Method 3. Run the Command Setup/Prepare AD
A user can execute Setup/Prepare AD command from Exchange Server CD to prepare Active Directory Service for MS Exchange 2010. Basically, this command helps to repair & recover MS Exchange server configuration automatically in AD. To carry out the task, follow the steps discussed below:
At first, Start Exchange 2010 Help.
- Go to Contents tab >> Select Deployment >> Click New Installation >> Select the option “Preparing to Deploy Exchange 2010”.
- Now click on How to Prepare Active Directory and Domains.
Method 4. Fix an Error “Failed to Mount Database Exchange 2013”
Users face some unexpected situations when failed to mount database Exchange 2013 or 2016, 2010, 2007 through manual way. Therefore, in order to overcome all the limitations and to have foolproof solution, one can go for professional third party tool. There are plethora of applications available online which can help in repairing corrupt Exchange 2013 database.
Conclusion:
MS Exchange is equipped with many advance features and allow users to store the database in an easy and simple way. However, there are some issues related with the server like “Not Able to Mount Database Exchange 2013, 2010, 2007 etc.” So, from the above blog we came across multiple manual ways with expert trick to fix and repair this problem.
