How to Resolve the Error: Failed To Communicate With the Mailbox Database?

Summary: In this write-up, we will provide solution and guide users to resolve the error: “can’t remove move request – failed to communicate with the mailbox database”. After fixing the error, users can easily move Exchange database mailboxes to the other server.

When Exchange Administrator or users tries to move Microsoft Exchange Server mailbox to another server due to storage space limit, low size on the destination server, etc… this error occurs. While migrating the mailboxes by using the New-MailboxExportRequest command from the existing Exchange Server to the new server, the migration process fails due to permission as well as connectivity issue and many more reasons.

The error message is displayed “failed to communicate with the mailbox database” when the migration of Exchange mailboxes failed. This issue can also occur when users try to remove the remove request command.

Here, we will provide various solutions to fix the error via Microsoft Exchange utilities. Additionally, discuss about the advanced software provide by SysTools i.e. Exchange Server Recovery Software that easily migrate offline/dismounted Exchange database mailboxes to the Live Exchange Server 2016 / 2013 / 2010 / 2007 / 2003 mailboxes in a simplified manner.

Use the Solutions to Solve the “Failed to Communicate With the Mailbox Database” Error?

Users can use the following solution to fix the error and after that you can again try to move the mailboxes to the another Exchange Server. Therefore, if the provided solution doesn’t help in that case users can use the professional Exchange Server Recovery software to do the migration in a hassle freeway.

This Recovery Manager for Exchange database tool doesn’t require any commands and permissions other than some Exchange Server credentials. It provides an interactive graphical user interface that makes the work of users a lot easier. The software easily resolves database corruption Exchange 2010, 2013, 2016 and repair EDB file with the help of the scan mode option of this utility. Then users can extract mailbox from EDB file Exchange 2016/2013 along with data items and export them to the Exchange Server mailboxes.

Solution 1: Check Permission

To migrate the Exchange mailboxes first users have to provide permissions and assign roles like – Mailbox Import Export and. If certain permission isn’t assigned then users have to face the error “failed to communicate with the mailbox database”. Here, you can provide the permissions to execute the export mailbox request to migrate the Exchange database mailboxes.

Use the AD (Active Directory) to assign the required permission given below:

1. In the Active Directory, go to View >> Enabled Advanced Feature
2. Find the mailbox migration user account
3. Select properties > Navigate to Security > Advanced
4. Click on the checkbox i.e. “Allow inheritable permission…” > Then, select the OK two-times > Save settings
5. Restart destination Microsoft Exchange Server > Then, try to migrate the Exchange EDB mailboxes

Solution 2: Check Network Connection & Destination Server

Network issue also create problem sometime when user move the mailbox to another server. In order to continue the migration process, check the network connection and along with this very the server port. Also see that the destination Exchange Server is active & running.

Solution 3: Remove Move Request By Using ADSIEit.msc

If the migration of mailboxes fail, this may be because the export request is stuck or pending. In that case, users can use the ADSIEdit.msc to remove the request.

Remove the request by using the steps given below and resolve the error:

1. Open Run dialogue box by using Windows + R key > Insert ADSIEdit.msc > Click on the OK button

2. After that, Go to the Connect to > Default Naming Context > DC = {your domain} > DC = {your domain extension}

3. Find the user account which is affected > Right click on it

4. Select properties > Click on filter button > Click on this check box “Show only attributes that have values”

5. Search the following entries:

– “msExchMailboxMoveRemoteHostName”

– “msExchMailboxMoveFlags”

– “msExchMailboxMoveStatus”

6. Select the Edit button > Click on Clear button > Repeat upto all 3 entries are cleared

7. Select the “OK” button

This solution helps users to remove the pending request.

Bringing It All Together

Now users can fix the error “failed to communicate with the mailbox database” by using the solution provided in this write-up. This error occurs while migrating the Exchange database mailboxes to another Exchange Server and to avoid the complexity to resolve the issue users can use the Exchange Server Recovery software which easily moves the offline EDB mailboxes to the Live Exchange Server in a simplified way. Also, if your Exchange database file is severely corrupted / damaged / unhealthy then with the help of this advanced tool you can remove the corruption and bring back the EDB file into the healthy state with no data loss.