In Exchange Server, mounting a database refers to bringing the database online so that it becomes accessible to users. It and enables them to easily exchange emails and use their contacts, tasks, or calendars. However, when mounting an Exchange Server database, you may often come across several issues that prevent you from mounting the database.
These errors prevent users from using mailboxes and affect email communication within and outside your organization. To avoid significant loss of reputation and financial drain, paying prompt attention to these issues is crucial. Here is a detailed insight into these errors, followed by their proven resolutions. Let’s begin with the reasons behind these Exchange database fails to mount errors.
What are the reasons behind the Exchange database mounting issues?
Numerous factors account for the mounting error in the Exchange database. Here are some of the most common ones:
- Shortage of space in the hard disk used to store the database
- A damaged or corrupt database caused by a server crash, sudden system shutdown, etc.
- Installation of an incompatible antivirus or backup software
- Attempt to mount databases in addition to the licensed Exchange Server limit
- A malware installed in the disguise of third-party software, deleting crucial Exchange Server files
Issues arising during Exchange Server Database mounting and their resolution
Here are a few critical issues that lead to a failed Exchange database mounting, along with their resolution. As an admin, you should be aware of them.
Dirty Shutdown state
The Exchange Database can show a dirty shutdown state due to missing or inconsistent log files. The reason could range from an incomplete transaction to power failures to an improper system shutdown, and so on. Here are the ‘Exchange database fails to mount’ errors that you may come across in this situation:
- JetError -501, JET_errLogFileCorrupt, Log file is corrupt: It indicates an I/O corruption, which leaves the database in a corrupted state. To resolve this issue, you will need to restore the database from a recent good backup.
- JET_errMissingLogFile: The error can be a result of an unexpected system shutdown because of a power outage. It can also result from the administrator changes to log files or because of corrupted backup software.
- JET_errLogFileCorrupt (501): It results when the Exchange Server finds a missing or corrupted transaction log file, disabling the database from mounting.
- JET_errDatabaseDirtyShutdown: It indicates an incorrect shutdown and results from a lost I/O flush on shutdown or administrator-modified logs.
The resolution for all these dirty shutdown errors is to restore the Exchange database from a known-good backup. Here are the steps to restore the database affected by the aforementioned mounting errors.
- In the Exchange Management Shell (EMS), use the below Eseutil command to determine the current database state: Eseutil/mh
- If you get a Dirty Shutdown, start the Eseutil SoftRecovery process to commit the uncommitted changes by using Eseutil/r cmdlet
- Check the database state again.
- If it is still Dirty Shutdown, use the Eseutil/p command to perform the hard recovery. This method will eliminate the corrupt and inconsistent log files to clean the database and set it free from the Dirty Shutdown state. However, it can also delete your crucial data, which is essential for the functioning of your business. Hence, always be cautious before opting for this method.
Insufficient resources on the server
To mount the database, your backup software should be compatible with the Exchange Server. Failing it will lead to uncommitted and transaction logs, leaving them retained in the Exchange. One after another, these uncommitted logs will occupy the complete disk space, resulting in the JET_errFileAccessDenied when you try to mount the database on the Exchange Server. The JET_errFileAccessDenied error occurs when your database becomes inaccessible due to insufficient disk space. Here is how you can fix this error:
- Use Windows Server Backup (WSB) or any other backup software.
- Make sure it is compatible with your Exchange Server
- Run the software to purge the uncommitted log files automatically to free the disk space
- Later on, you may set some space manually by exporting the mailboxes to PST files
- Likewise, you may also archive old mailboxes to set the disk space free
Exchange Services not running
If, while mounting the database, some Exchange Services stop running, it can also cause mounting issues. The following errors are likely to surface in this situation:
Error 1: The Microsoft Exchange Information Store Service (Store.exe) may stop functioning because of a deadlock in the service, mostly in the case of Exchange Server 2010.
Resolution: To fix this issue, install the Update Rollup 4 for Exchange Server 2010 Service Pack 2
Error 2: Exchange services not running. Please start all required Exchange services.
Resolution: Start the stopped Exchange Services
- Open the Server Manager
- Click Tools > Services
- Ensure that all the Exchange Services are running
- If you notice any service in the stopped status, right-click on it and select Start to start it.
Alternatively, the following PowerShell command can also resolve the issue:
Get-Service *Exchange* | Where {$_.DisplayName -notlike “*Hyper-V*”} | Restart-Service –Force
After starting the required services, mount the database again on the Exchange Server.
Error 3: Event ID 1005 – Information Store cannot be started.
Resolution: Try to start the stopped services as you have already done to resolve Error 2.
Insufficient permissions
You may face the ‘Exchange database fails to mount’ errors due to the lack of requisite permissions.
Resolution: Ensure to have full control of the database you want to mount. Here are the steps for the same:
- Open the Windows Explorer to look for the Exchange database folder
- Right-click on the folder > Properties > Security
- Set the following permissions:
-
- Administrators: Full Control
- System: Full Control
Log files quarantined by Antivirus software
If our antivirus is not configured properly or is incompatible with your Exchange Server, it can do more harm than good to your database. It can mark your database log files as malicious activities, like a log-injection attack, ransomware, or Trojan dropper. Eventually, it will quarantine the files. As a result, you get the ET_errFileAccessDenied error when trying to mount the database.
Resolution: Make sure that your antivirus application is compatible with your Exchange Server versions. Alongside, configure its settings properly so that it does not blacklist your log files and protect them from isolation.
Using Exchange recovery software to fix Exchange Database Mount Failure Issues
The proven fixes discussed for the database mounting issues can work effectively. Nevertheless, they do have several limitations in terms of time consumption, data loss, and technical expertise. If you are a pro in your field, you can just nail it. However, if you do not match that level or just do not want to waste time in leveraging manual methods, just try any of the Exchange recovery software. You can have many of them online, and Stellar Repair for Exchange is one of them. To know more about this software, browse through the company’s website.
Conclusion
When using an Exchange database, you may face numerous mounting issues that are crucial to resolve. These errors can result from system crashes, power outages, misconfigured antivirus software, or even from missing or corrupted log files. Whatever the reason, these issues can bring your business to a standstill if you do not take timely action.
The need is to know about the exact issue and fix it properly. If it is a dirty shutdown, try to restore the database by using a healthy backup. If the server has a lack of disk space, purge the unwanted or old data from the server. In case an Exchange service is not running, install the requisite update to restart it, or open the Server Manager and start the stopped services. Likewise, many more errors that exist would need concrete resolution.
At times, you may find these manual methods time-consuming, ineffective, or too technical. In any such event, you can opt for the Exchange recovery software. An automated tool, such as Stellar Repair for Exchange, can work effectively in resolving these ‘Exchange database fails to mount’ issues.
Anantha Nageswaran is the chief editor and writer at TheBusinessBlaze.com. He specialises in business, finance, insurance, loan investment topics. With a strong background in business-finance and a passion for demystifying complex concepts, Anantha brings a unique perspective to his writing.
