{"id":63520,"date":"2020-08-28T04:41:42","date_gmt":"2020-08-28T04:41:42","guid":{"rendered":"https:\/\/www.stellarinfo.com\/blog\/?p=63520"},"modified":"2024-04-16T10:54:08","modified_gmt":"2024-04-16T10:54:08","slug":"resolve-unable-mount-database-hr0x80040115-error","status":"publish","type":"post","link":"https:\/\/www.stellarinfo.com\/blog\/resolve-unable-mount-database-hr0x80040115-error\/","title":{"rendered":"How to Resolve unable to mount database. (hr=0x80040115, ec=-2147221227)"},"content":{"rendered":"

To mount a database (EDB) file in Exchange Server, Mount-Database<\/a><\/strong> cmdlet is used, which is available only in on-premises Exchange. However, the cmdlet mounts database only if the Microsoft Exchange Information Store Service and Microsoft Replication service are up and running.<\/p>

Also, the user account should have permissions assigned to run Mount-Database<\/strong> cmdlet to restore a dismounted or offline database file. If the user doesn’t have sufficient permissions, required Exchange services are down, or database is corrupt, a database mounting error occurs, such as,<\/p>

MapiExceptionNetworkError: Unable to make admin interface connection to server. (hr=0x80040115, ec=-2147221227)
Diagnostic context:
……
Lid: 15000 dwParam: 0x6BA Msg: EEInfo: prm[1]: Pointer val: 0x0000000000000000
Lid: 15000 dwParam: 0x6BA Msg: EEInfo: prm[2]: Pointer val: 0x1600A8C000000000
Lid: 16280 dwParam: 0x6BA Msg: EEInfo: ComputerName: n\/a
Lid: 8600 dwParam: 0x6BA Msg: EEInfo: ProcessID: 124904
Lid: 12696 dwParam: 0x6BA Msg: EEInfo: Generation Time: 2014-02-26 21:31:54:96
Lid: 10648 dwParam: 0x6BA Msg: EEInfo: Generating component: 8
Lid: 14744 dwParam: 0x6BA Msg: EEInfo: Status: 10060
Lid: 9624 dwParam: 0x6BA Msg: EEInfo: Detection location: 318
Lid: 13720 dwParam: 0x6BA Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x6BA Msg: EEInfo: NumberOfParameters: 0
Lid: 24060 StoreEc: 0x80040115
Lid: 23746
Lid: 31938 StoreEc: 0x80040115
Lid: 19650
Lid: 27842 StoreEc: 0x80040115
Lid: 20866
Lid: 29058 StoreEc: 0x80040115
Exchange Management Shell command attempted:
‘Mydomainname.local\/OurBusiness\/Users\/test’ | move-mailbox -TargetDatabase ‘SERVERNAME\\First Storage Group\\Mailbox Database’
Elapsed Time: 00:00:45<\/em><\/p>

In such cases, you may follow the below discussed manual methods to repair, restore and mount the database through command line tools or use a GUI based Exchange recovery software, such as Stellar Repair for Exchange, to recover mailboxes from damaged database and restore them to a healthy database on a Live Exchange server directly in a few clicks.<\/p>

\n
\"download\"<\/a><\/figure>\n<\/div>

Methods to Resolve Unable to Mount Database (hr=0x80040115, ec=-2147221227)<\/h2>

Follow these methods and workarounds to fix the “MapiExceptionNetworkError: Unable to make admin interface connection to server. (hr=0x80040115, ec=-2147221227)” error.<\/p>

\n

NOTE: <\/strong>If you are trying to mount a database file copied from another server for DAG and failover protection, use the following command before mounting the EDB file,<\/p>\n<\/blockquote>

Set-MailboxDatabase DB01 -AllowFileRestore $true<\/code><\/pre>
Method 1: Check Database State<\/h3>
You can’t mount a database which is in Dirty Shutdown state<\/a>. Thus, it’s important to check and bring the database to the Clean Shutdown state, before mounting it. To check whether the database is in Dirty Shutdown or Clean Shutdown state, run the following command in PowerShell as an administrator,<\/p>
eseutil \/mh \"PATH TO EDB FILE\\MyDatabase.edb”<\/code><\/pre>
\n
\"check<\/figure>\n<\/div>
If the output displays State: Dirty Shutdown<\/strong>, you need to bring the database to Clean Shutdown state to mount it successfully and avoid the error MapiExceptionNetworkError: Unable to make admin interface connection to server. (hr=0x80040115, ec=-2147221227).<\/p>
\n
\"dirty<\/figure>\n<\/div>
Use the following PowerShell command to fix the database and bring it back to the Clean Shutdown state.<\/p>
eseutil \/p \"PATH TO EDB FILE\\Database.edb”<\/code><\/pre>
After executing this command, use the following command to again check the shutdown state of database. It should be State: Clean Shutdown<\/strong>.<\/p>
eseutil \/mh \"PATH TO EDB FILE\\MyDatabase.edb”<\/code><\/pre>
\n
\"clean<\/figure>\n<\/div>
After restoring the database to clean shutdown state, check the log files.<\/p>
Method 2: Check Log Files<\/h3>
To check the database log files, run the following command in PowerShell,<\/p>
eseutil \/ml \"PATH TO LOG FILE\\Mailbox Database\\E00\"<\/code><\/pre>
In this command, E00<\/em><\/strong> is the starting sequence of the logs.<\/em><\/p>
If the output displays a list of log files with the status of log files as OK, <\/strong>then try re-mounting the database.<\/p>
\n
\"check<\/figure>\n<\/div>
In case the database shutdown state is Clean and log files are OK, but the database still does not mount, follow this guide, Is your Exchange database as in a ‘Clean Shutdown’ state? But it is not mounting?<\/a><\/p>
Method 3: Check Exchange Services<\/h3>
If the database mount fails even when the database is in clean shutdown state, check and confirm that the following Microsoft Exchange services are up and running,<\/p>
    \n
  1. Microsoft Exchange Information Store Service<\/li>\n\n\n\n
  2. Microsoft Replication Service<\/li>\n\n\n\n
  3. Microsoft Exchange System Attendant<\/li>\n<\/ol>
    \n
    \"restart<\/figure>\n<\/div>
    To view these services, press Windows+R<\/em>, type services.msc<\/em> and press ‘Enter<\/em>’ or click ‘OK<\/em>’.<\/p>
    If these services are not running, right-click on the service and choose Restart<\/strong>.<\/p>
    Method 4: Defragment the Database<\/h3>
    You may also perform Exchange database defragmentation<\/a> to optimize the database file and prepare it for mount. The command is as follows,<\/p>
    Eseutil \/d “Database File Path\\database.edb”<\/code><\/pre>
    Method 5: Recover Database<\/h3>
    Further, you may try to perform Soft or Hard Recovery on the database. Soft recovery eseutil\/r<\/a> is safe and can be performed by using the following command,<\/p>
    Eseutil \/r \/l \"PATH TO LOG FILES\\E00\" \/d \"PATH TO DATABASE FILE\\Database.edb\"<\/code><\/pre>
    However, hard recovery eseutil\/p<\/a> could cause problems and thus, not recommended unless you have database backup.<\/p>
    \"Stellar\"<\/figure>
    Method 6: Use Exchange Recovery Tool<\/h3>
    To restore offline or dismounted database, you can use an Exchange database repair software, such as Stellar Repair for Exchange. If none of the methods work, it could be a case of damaged or corrupt database. Thus, you need an Exchange recovery tool<\/a> to repair damaged Exchange database files and recover corrupt, dismounted, or offline database files.<\/p>