Getting an error with New-MoveRequest to a newly created database on Exchange 2019

Question

I created a new database in Exchange 2019 and when trying to move a mailbox to the database we get the error message:

Failed to communicate with the mailbox database. There is no support for this operation.

• CategoryInfo : ResourceUnavailable: (:) [New-MoveRequest], NoSupportException
• FullyQualifiedErrorId : [Server=SERVER,RequestId=59ca2060-cb31-4894-b450-cbbff06a308a,TimeStamp=4/2/2021 7:48:44 PM] [FailureCategory=Cmdlet-NoSupportException] 5A29C5C1,Microsoft.Exchange.Management
  .Migration.MailboxReplication.MoveRequest.NewMoveRequest
• PSComputerName : domain name

It does not work with ECP or powershell. And we have tried moving multiple different mailboxes.

Any suggestions on how to resolve this?

Thank you

Answer 1

Hi. This article solved the issue.
https://learn.microsoft.com/en-us/exchange/troubleshoot/migration/cannot-access-move-mailbox

You have to update the Schema of Database

Update-DatabaseSchema DB01
Dismount-Database DB01
Mount-Database DB01

Greg

Answer 2

@Holly Boyer

Could you provide more detailed information about the topology of your organization and the command that you used? It may could help us narrow down this issue.

I would suggest you try to create a new mailbox on this database, check whether could create successfully. If you cannot create mailbox on this database, it means there exist issue with this new database or the connection between your Exchange server and database.

If you could create new mailbox on this database, I would suggest you try to migrate another mailbox to this database, check whether there exist issue with the mailbox that you want to migrate before.

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

If you are a "DAG" member while creating a new database, you may be experiencing this problem.

After much effort, I was able to solve my problem.

The schema version of the new database I created before solving the problem was as follows

I couldn't migrate to this database from a different database because it had the "0.121" schema version.

Then I deleted the database I created.

Then I removed one of the Exchange servers from DAG membership.

Then I created a new database on the server that was removed from the "DAG" membership.

Then the schema version of the database I created was as follows. So as it should be.

Then I made the server a "DAG" member again and the migration no longer gives an error.

Good luck!