Mostly Exchange Administrator become stumble when they are not able to access the Database while mounting the EDB file. Since while an attempt is made to mount or connect the database to Exchange server, certain issues can arise and in order to address the situation, we have decided to focus on issues regarding Exchange Database Not Mounting and their solutions. In the latter section of this post, readers can solve issues occurring when the database does not get connected to Exchange Server.
We try to combine all the problems faces by most of the Exchange Administrator into Three-Section, first one section related to Hardware issue of the environment where Exchange Application is installed. In other section, we try to find issues related to Active Directory problem and at last, we deal with corruption issues of Exchange Database.
Hardware Related Issues: Since All database stored in Physical memory and hardware issue arise database will not mount to Exchange server and resulted to access issues. Sometimes problems occurred due to lack of space in hard-disk, even corruption due to the power outage can lead to database mounting issues.
they are switching from Lotus Notes to Exchange Server by converting their Lotus Notes NSF files to PST format that can be imported in Exchange mailboxes using the Import Wizard to view the mailboxes
Power Outage: If the power supply to an exchange database stops abruptly, the database will shut down. Next time when it will be switched on, it may not function properly due to the corruption led by sudden shutdown.
Space Shortage: In every Exchange Server, there is a limit of how much data the server can store. When the data size reaches that limit, problems started to occur. It can also create issues while users try to mount the database. Even sometimes after adding space while working on VM (Virtual Machine), Administrator not able to access the mailboxes and get an error related to Shutdown after running the Powershell Commands to check the state of Database
Follow to Solve Exchange Database Not Mounting via Powershell
1) Run command: eseutil /mh “Path of Database”
Ex: eseutil /mh “C: Program Files\ MDB DATA \ Priv.edb”
2) If In the Result you get “Dirty Shut-Down State” then Check the Status Whether log file required or not: IF “Yes” then make sure that the required logs file should be in “Clean State”.
3) For that, Run Eseutil Command “mh” Such as
Ex: eseutil /mh “C: Program Files\ MDB DATA \ e00”
4) IF the Result you find “ No Damaged to Log Files” then you proceed further:
Now we follow the procedure for “Soft Recovery” for that we use “Eseutil /r Command”
Ex: eseutil /r <Log Prefix> / Path of Log files / d “Path of Database”
5) Such as eseutil /r e00 /l ““C: Program Files\ MDB DATA” /d “C: Program Files\ MDB DATA”
If you get Error Code -1216, mostly user face this event id error issues then it causes due to “ JET_ errAttached DatabaseMismatch”.
Then you need use Eseutil /i Command In Soft Recovery Case.
For Hard Recovery: Exchange Administrator can run commands “Eseutil /cc” if the logs are not in “Clean State”
In order to mount a database, Information Store needs the machine account to have read permission to the Information Store. Lack of permission may also lead to the appearance of Exchange Database Not Mounting error. When any inherited or explicit Server permission is altered or a machine is terminated from DS group, it affects database mounting to exchange. Overall, if a server is absent in a particular Active Directory, it can cause trouble in database mounting.
Solutions: Make sure that some of the important objects like CN=AdminGroupName, CN=Services, CN=InformationStore, CN=Servers, etc., are present in Active Directory. To check, users can run Exchange setup in DomainPrep mode or use ADS Edit Tool. This editing tool can also be used when Security Principals container is removed.
Like every other component of Computing, Exchange server database is also prone to corruption. These corruptions can occur at different levels and hamper the mounting process of the database to the server.
Instant Solution: Users can use the SysTools Exchange Server Recovery Software that easily recovers & repair Exchange database from corruption with no data loss. It provides dual scanning mode option i.e. Quick and Advance scan which easily recover corrupted Exchange mailboxes and EDB file automatically without any trouble and users can export the recovered EDB to PST, MBOX, HTML, MSG, PDF, HTML file formats. Also, you can easily export the mailboxes to Live Exchange Server and Office 365.
Antivirus Interfering to Modify Transaction Log Files: Antivirus programs often have a clash with different essential components of a system and database. For example, if an antivirus program is designed to scan transaction log file, it might end up detecting some of the files as virus. Subsequently, the antivirus will modify or delete the flagged log files and cause database corruption. During database corruption caused by antivirus interference, these two error messages can occur:
Event ID: 455 : Description: The following message is usually accompanied with the event (Information Store (1892) b2a6f816-2baf-462e-918c-eda5d1fb24d3: Error -1811 (0xfffff8ed) occurred while opening log file C:\Program Files:\Exchsrvr\mdbdata\E00.log)
Event ID: 9518: Description: (Error Current log file missing starting Storage Group /DC=COM/DC=EXAMPLE/CN=CONFIGURATION/CN=
SERVICES/CN=MICROSOFT EXCHANGE/CN=FIRST ORGANIZATION/CN=ADMINISTRATIVE GROUPS/CN=FIRST ADMINISTRATIVE GROUP/CN=SERVERS/CN=COMPUTERNAME/CN=INFORMATIONSTORE/CN=FIRST STORAGE GROUP on the Microsoft Exchange Information Store. Storage Group — Initialization of Jet failed.
Solution: Go to the settings of your Antivirus software and make sure it does not scan transaction log files of Exchange database, even this small mistake doesn’t allow the user to mount the database in Exchange.
Event ID 474: Error message with this event id signifies page level corruption in Exchange database. Usually, this corruption is caused by page checksum mismatch.
Solutions If users have an updated backup of the database, they can format the hard drive and then restore the backup data. Otherwise, they can take the help of eseutil/P, eseutil/d, and isinteg –fix Powershell commands to repair Exchange Database.
Event ID 517: When the Exchange database corruption occurs due to missing log files, event id 517 may appear. These missing log files can be the result of human error or backup application.
Solution: To get rid of this problem, copy the log files and save them to another directory. Turn on “circular logging” to remove all the log file. Now the database should not have any problem to mount. At this point, users can switch off circular logging and backup the complete database.
As various reason can occur due to which exchange database not mounting and the user can’t access their mailboxes, so to fix it Exchange Administrator need to know the exact problem that can be related to the above-mentioned issue and use above solutions regarding Exchange database mounting. However, the causes of not accessing the Exchange Database issues can occur due to other issues, are not limited to the mentioned one and can be asked in Exchange forums for better solutions and to recover offline / dismounted Exchange database file from corruption without any interruption users can use the advanced software mentioned here.