How to Fix Error MapiExceptionNetworkError Unable To Mount Database (hr=0x80040115, ec=-2147221227)? Find the Solution

Summary: This write-up will guide you to resolve the error mapiexceptionnetworkerror unable to mount database (hr=0x80040115, ec=-2147221227) by using the solution provided here.

Sometime when an IT administrator or Exchange user tries to mount the dismounted Exchange database file then they will encounter the database mounting error. This generally occurs when Microsoft Exchange Server has not enough space when the database is not in a clean state, corruption issue, and many other reasons.

They receive the following error:

Solutions to Fix Error MapiExceptionNetworkError Unable To Mount Database (hr=0x80040115, ec=-2147221227)

To mount the Exchange database use the solution given in the below section and resolve the Error: MapiExceptionNetworkError: Unable to make admin interface connection to server. (hr=0x80040115, ec=-2147221227).

Solution 1: Check Exchange System Attendant Service

This service is one of the core components of the Microsoft Exchange Server services. So, it is important to check weather it is working properly or not. If you find that something wrong with Exchange System Attendant Service, then right-click on it and click on restart.

Note: User can check the Exchange Information Store and Replication Service. It if is not running then do the same as you do with the Exchange System Attendant Service.

Solution 2: Check the State of Exchange Database

It is very important to check the Microsoft database state because the database is not in clean shutdown state then the first user have to recover the Exchange dirty shutdown state to mount it back.

Follow the command given below to check the state of MS Exchange database state:

Get-MailboxDatabase Status | % {eseutil /mh $_.edbfilepath }

Output:

The result shows on the screen is that the state of the database if dirty shutdown and to mount the Exchange database again, users need to bring back the state into a clean shutdown. Then you resolve the error MapiExceptionNetworkError: Unable to make admin interface connection to server. (hr=0x80040115, ec=-2147221227).

In the screenshot, it is showing that there are missing log files and to recover it back you have to perform the soft recovery in Exchange database by using ESEUTILutility.

Insert the command given below:

After that check the log file heath by using the cmdlet given below:

Resultant File:

Check one more time the state of the database

As you can see that the Exchange database is in a clean shutdown state. You can mount the database again.

Note: If the soft recovery is unable to change the database state i.e. Dirty Shutdown. Then use can perform hard recovery command – eseutil /p “enter the database path” . After that user need to defrag Exchange mailbox database by inserting the cmdlet – eseutil /d “name of the database” . At last, you have to use the Isinteg command – Isinteg –s “server_name”  -fix –test alltests to check the database integrity.

But it is highly recommended not to perform hard recovery because in this process user will face huge data loss and it will hard to predict how much data is lost. Users can use the professional solution i.e. Exchange Recovery Software provided by SysTools to fix the dirty shutdown error by repairing the Exchange database file.

Solution 3: Use Professional Solution

Exchange Recovery Software recover the offline / dismounted Microsoft Exchange database file and  repair Exchange mailbox from corruption. The utility provides scan mode option (Quick and Advance scan) that removes corruption and repair EDB file with no data loss. By default, the EDB file goes through quick scanning mode which recovers minor corrupted .edb file, and for the high corruption, the user can select the advance scan mode.

After selecting this option the software which resolve database corruption Exchange 2010, 2013, 2016 and repair the Exchange database without losing single bit of data, then the user can mount the database and the Error: MapiExceptionNetworkError: Unable to make admin interface connection to server. (hr=0x80040115, ec=-2147221227) is solved.

The advance scan also recovers permanently deleted Exchange mailboxes (archive, shared, legacy, user, disconnected) and data items (emails, contacts, calendars, notes, journals, tasks) from the loaded Exchange database file. You can select this option and recover deleted mailbox after retention period. After repair the Exchange .edb file the tool export it directly to the Live Exchange Server, Office 365, and various file formats – PST, EML, PDF, MBOX, HTML, MSG.

The utility provides graphical interface which helps the user to perform their job easily and it doesn’t require any technical and in-depth knowledge to use the tool. Also, it allow you to recover purged mailboxes and items with no data loss.

It supports all version of Microsoft Exchange Server 2003, 2007, 2010, 2013, 2016, & 2019. After exporting the Exchange data the software auto-generates the export report which contains the success and fail count in CSV file format.

Key Features Of Automated Software

1. Recover and repair multiple corrupted EDB file
2. Extract data from public folders and private mailboxes
3. Preview MS Exchange mailbox items before conversion
4. Maintain actual folder structure and keep metadata intact
5. Remove encryption from Exchange mailbox i.e. (SMIME/OpenPGP) in batch
6. Recover purged data items and mailboxes stored in offline/dismounted Exchange database file
7. Extract mailbox from EDB File Exchange 2013/2016 to multiple file format
8. Compatible with Microsoft Outlook, Exchange Server, and MS Windows OS versions

Bringing It All Together

This write-up provides complete information to solve error mapiexceptionnetworkerror unable to mount database (hr=0x80040115, ec=-2147221227). When the user is unable to recover the database state from dirty to clean shutdown by using the manual solution provided here. Then they can use the professional solution described in the above section which helps them to repair the Exchange database easily without writing any cmdlet. When the mailboxes are repaired then you can easily mount the Exchange database.