Unable to Mount Database Exchange 2019, 2016, 2013, 2010
Each and every modification done in the Exchange Server database is recorded in the transaction log files. These files are very important for the normal functioning of the MS Exchange Server. However, if this log file is removed by the user accidentally before it is not written to the associated database, then can generate several issues. For example, failed to mount mailbox database in Exchange 2019, 2016, 2013, & 2010 or generates an error message i.e. unable to mount database (hr=0x80004005, ec=1108). Whenever a user tries to mount the database after, this is the common error encountered by the users.
Apart from this, there are some other errors also that can cause the “failed to mount database Exchange 2010” issue. One such reason is a dirty shutdown of the system. There is a high chance that a user may lose access to the crucial log files which leads to corruption in the Exchange 2010 database. All such types of situations create trouble in accessing the database.
Therefore, it becomes really important for the user to resolve the error: Failed to mount Exchange database 2016, 2013, 2010, 2007. This blog mentions different methods, both manual as well as automated solution to rectify this problem. It briefly describes a third-party solution i.e. SysTools Exchange Mailbox Recovery Software that easily allows to recovery of Exchange Mailbox database files and errors. This utility provides a scan mode option to resolve Exchange database corruption and repair corrupt EDB files without any loss of data in a simplified manner.
Common Error Message:
Following are the different types of error messages that a user can encounter while mounting the database into Exchange 2019, 2016, 2013, 2010, or 2007:
"Unable to mount database (hr=0x80004005, ec=-528). -------------------------------------------------------- Microsoft Exchange Error -------------------------------------------------------- Failed to mount database '<DatabaseName>'. <DatabaseName> Failed Error: Couldn't mount the database that you specified. Specified database: <DatabaseName>; Error code: An Active Manager operation failed. Error The database action failed. Error: Operation failed with message: MapiExceptionJetErrorMissingLogFile: Unable to mount database. (hr=0x80004005, ec=-528) . [Database: <DatabaseName>, Server: <ServerName>]. An Active Manager operation failed. Error The database action failed. Error: Operation failed with message: MapiExceptionJetErrorMissingLogFile: Unable to mount database. (hr=0x80004005, ec=-528) . [Database: <DatabaseName>, Server: <ServerName>] An Active Manager operation failed. Error Operation failed with message: MapiExceptionJetErrorMissingLogFile: Unable to mount database. (hr=0x80004005, ec=-528) . [Server: <ServerName>] MapiExceptionJetErrorMissingLogFile: Unable to mount database. (hr=0x80004005, ec=-528)"
Reason Behind “Unable to Mount Database (hr=0x80004005, ec=1108)”
There can be various possible reasons behind this error in Exchange and all of them are discussed below:
- The most common reason that generates this error is improper or dirty Shutdown of an application.
- If the log files are deleted before it has been written to the database, then also it generates this error.
- Corruption in the database of Microsoft Exchange Server 2016, 2013, 2010, 2007.
Methods to Fix Unable to Mount Database in Exchange Issue
If you are looking for a solution to resolve to mount database in Exchange 2016, 2013, 2010 & 2007 errors, then no need to worry. In this segment of the post, we have discussed four methods to fix this issue.
1: Check and Repair the Exchange Database
If the main reason behind the error is corruption in the Exchange database, then one first needs to check the database. After that, take it out of the dirty shutdown state. Therefore, in order to repair the data execute the following commands: eseutil /p. This command will help in repairing the corrupt Exchange EDB file stored at location:
"C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database\Mailbox Database10.edb"
After executing the repair EDB command, try to re-run the database and confirm the output state. In the case of Clean Shutdown, a user can mount the database. However, if there is some issue while mounting like popping up error messages appear ‘Unable to mount database log files” in exchange 2013, then check the database logs.
2: Check and Repair the Exchange Log File
If there is no issue in the Exchange EDB file, then a user needs to check the Exchange Log file. In addition, while checking the Exchange Log file, always specify the starting sequence of the logs and execute the following command: eseutil /ml. This is the command that helps users in repairing the Exchange Log File.
"C:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database\E00"
After executing the above command, it will list all logs along with their state. It can be possible that a user might receive an error. But, if there is no issue with the log files, then one can switch to Method 3 to resolve this error.
3: Run the Command Setup /Prepare AD
One can execute the Setup /Prepare AD command from the Exchange Server CD to prepare the Active Directory service for MS Exchange 2010. This command is basically used to repair & recover the MS Exchange Server configuration in the AD automatically. In order to do the same, follow the steps mentioned below:
In Microsoft Exchange Server 2010
- First of all, start the Exchange 2010 Help
- Then, navigate to Contents tab >> Deployment >> New Installation >> Preparing to Deploy Exchange 2010 option
- After that, click on How to Prepare Active Directory and Domains
4: Solve Error ‘Unable to Mount Database’ Using Automated Tool
There are some situations in which a user fails to mount database Exchange 2019, 2016, 2013, and 2010 via manual method. Therefore, to overcome all the limitations and to have a foolproof solution, one can use the professional solution by SysTools.
The utility provides advanced features (Quick & Advance scan) that easily remove corruption from EDB files & retrieve the Exchange mailbox database without any loss of data. The Quick scan option recovers Exchange database files from minimal corruption and for severely corrupted EDB files select the Advanced scan.
Moreover, one can easily recover all data from the Exchange Mailbox without compromising data integrity. Apart from all this, the software after recovering the EDB file exports it to PST file format also. This will increase the accessibility of Exchange EDB files.
The software provides an option to export data to Live Exchange Server and Microsoft 365. You can also extract mailboxes from EDB to PST, MBOX, PDF, EML, MSG, and HTML files. After conversion, the tool auto-creates the export report which contains the success and fail count of export EDB mailbox data. This software supports all versions of Exchange Server, Microsoft Outlook, and Windows OS.
To Wrapping It UP
Microsoft Exchange makes it convenient for users to store the database and come along with several interesting features. However, there are some errors associated with this such as “unable to mount database in Exchange 2010.” Therefore, in the above blog, we have learned some manual solutions along with an expert trick to fix this problem.
Frequently Asked Questions
Can lack of disk space cause my server to dismount?
The primary purpose of the Exchange Server is to process and hold all email communication. For that, it requires a significant storage capacity.
If you fail to upgrade server hardware on time and let old emails build up, then soon you will find that the Server can no longer fetch more emails.
In such a scenario, it becomes highly likely that your server dismounts.
You can check the current storage status with a simple PowerShell command:
In a new PowerShell instance, paste:
Get-PSDrive –PSProvider FileSystemCopy Code
This will display how much of the total volume is still free and where exactly the data is kept.
If you believe that storage is nearing its maximum capacity, delete old data or upgrade the hard disk.
None of the common errors seem to trigger dismounting in my server, then why does it fail to mount?
If this is the case, check your antivirus program. Third-party programs like antivirus may do a false positive trigger on a harmless file and dismount your database.
Additionally, your Exchange server may also see the program as a threat and dismount it to protect the data.
To prevent such a thing from happening, ensure that the antivirus you get is compatible with the environment you are placing it in.
