Database won't mount

Hope you have the backup of the Exchange Database.

Please Stop Exchange Information Store Service and move the trasnaction logs to other folder and start the Exchange Information Store Service, then check whether Database getting mounted or not.

Reboot your exchange server if you haven't already done that. Also make sure that space isn't and issue with the DB.

Error -1018 indicates corruption in the database EDB file, however you can try the above options.

Make sure there is no disk issues or failure events.

Otherwise you may restore the database from backup or copy a flat file of the EDB on another location and run the hard repair on it.

Note: There is a chance of data loss in running hard repair.

If you are running exchange 2010 you only need to run hard repair and it is recommended after hard repair you can move mailboxes on another database i.e. new database.

You can also mount the production database with blank edb file if the database is hugh in size and hard repair might take a lot of time to complete so that users still receive new email in their outlook.

Once the hard repair is complete you can use the dial-tone procedure and merge both the old and new databases.

Try to mount using -force switch using EMS.

Hi,

You need to repair the database with the eseutil tool. First I will recommend you to use the soft repair.

When you run the eseutil /mh "name of the database"

You have the status in clean shutdown or dirty shutdown?

Regards
Valentina

This is a common issue which may occur when you remove log files that has not been committed to the associated database, which may lead to many serious problems.

You can solve this problem by removing all previous log files and moving transaction log files to a different folder, but before that you need to check database consistency state. For that follow these steps below:

1. Stop Information Store Service of Exchange and halt all databases in the storage group.

2. After that you need to verify the integrity of the database for that run Eseutil /mh command and examine the ‘State’ value under its header information.

3. If the database is in consistent state, you can safely remove all transaction log files and save them to a different folder but make sure you don’t remove the current transaction log files.

4. If the database is in inconsistent state, restore from the last backup.

5. If backup is invalid, run Eseutil /r command for soft recovery.

6. If still it display error, run Eseutil /p command for hard recovery but this hard recovery may cause you data loss as it deletes all the corrupt pages.

If your problem is still not getting resolved after trying all the possible manual methods, then it would be better for your try professional Exchange Recovery Software.

Firstly try soft repair by using eseutil /mh as well as eseutil /r & eseutil /ml.
Try to move the log files under the database to another location.
Then you should restore from backup.

Also get help from this article to fix Exchange 2016/2013/2010 Error Unable to Mount Database.

Thank you all. Problem solved by moving to G Suite. I'm done with Exchange Server!