How to Solve Source Mailbox Already BeingMovedPermanentException Error?

Written By Ravi Singh
Approved By Shaun Hardneck
Updated on 16 May, 2024
Min Reading 5 Min
Share

Table of Content

Summary: When trying to move mailboxes from on-premises Exchange Server to Exchange Online in a hybrid environment, you might receive an error message, like “SourceMailboxAlreadyBeingMovedPermanentException.” In this post, we are going to discuss this error message and the ways to fix it. You’ll also find about a professional EDB converter software that can help migrate mailboxes and other resources from Exchange database to Office 365 in a few simple steps, without any issue.

Free Download

Read full summary

There are various methods to migrate mailboxes from on-premises Exchange Server to an Office 365 tenant. These include Cutover, Staged, Minimal Hybrid, and Full Hybrid. In a Hybrid environment, both Exchange on-premises and Exchange Online work as one. This method is ideal if you don’t want any interruption during the migration of data. However, sometimes, when trying to move a mailbox or mailboxes from on-premises to Exchange online, you might receive the following error messages (or similar):

Error: UserAlreadyBeingMigratedException: The user ‎’mailbox’ already has a pending request. Please remove the existing request and resume the current batch or start a new batch for this user. –> Mailbox ‎’Name’ is already being moved to ‎’office 365 database‎’.

Error: MigrationPermanentException: The onboarding move could not be created because user ‎’mailbox’ is already being moved. –> The onboarding move could not be created because user ‎’mailbox‎’ is already being moved.

However, if there is a previous move which was in process or has failed/stuck, then you will get a similar error.

The error “SourceMailboxAlreadyBeingMovedPermanentException” would be different, depending on the following scenarios:

If you receive the error message, “Mailbox ‘Name’ is already being moved to ‘<office 365 database>.”, it means that you had a move request done on a user. This will not allow you to move it. This happens when the user has an active or an orphaned move request in Exchange Online.
If you receive the error message, “The onboarding move could not be created because user ‘Name’ is already being moved”, it means that there is already an active or orphaned move request in your Exchange Server for the specific user.

Steps to Fix the SourceMailboxAlreadyBeingMovedPermanentException Error

Step 1: First, you need to identify if there are actual move requests for the user specified in the error. For this, you need to run the Get-MoveRequest command on both Exchange Server and Exchange Online.

For the local Exchange Server, open the Exchange Management Shell (EMS) and run the following command:

Get-MoveRequest -Identity 'user@contoso.com'

For Office 365, you need to run the same command by using the Exchange Online PowerShell.

In case you don’t know the identity of the user, you can run the command alone. It will get you all the move requests in Exchange Server or Exchange Online.

Step 2: Next, you need to verify and delete the move requests so that you can re-run the new move requests. You can verify the move request by checking the status. The status would be either completed or failed. You will need to remove the request manually to re-run a move. For this, you can use the Remove-MoveRequest command.

If the move of that user is part of a migration batch, you need to remove the whole batch or the user from the batch. Once done, this will remove the move request of the user.

If the error persists, then you need to remove the request manually for the user from the on-premises Active Directory Schema. For this operation, you need to use the ADSI Edit application. Here are the steps to do so:

Note: You need to keep in mind that when using ADSI Edit or Active Directory Attributes, you are editing the Active Directory Schema. Any changes or mistakes can have catastrophic repercussions on your Active Directory, Exchange Server, and other applications which are dependent on your Active Directory.

Open the Active Directory Users and Computers from your Domain Controller and locate the affected user.

Right-click on the user and click on Properties.
Click on the Attribute Editor.

Locate the attributes which start with msExchMailboxMove.
If any attributes are populated, you need to clear them off. This usually happens when there was a move request and it hasn’t cleared the attributes.

Note: There is no way to clear all the users at once or automatically through the GUI. So, this must be done manually.

Conclusion

The error “SourceMailboxAlreadyBeingMovedPermanentException occurs when moving mailboxes from on-premises Exchange Server to Exchange Online (Microsoft 365) in a hybrid environment. Above, we have discussed the steps to fix this error. If the issue persists, then you can take the help of a professional application, such as Stellar Converter for EDB to migrate the mailboxes. This application can open any Exchange mailbox database version of any size and export the mailboxes and other data granularly to PST and other formats. It can also export mailboxes from EDB file directly to another Exchange Server or Office 365 tenant. Stellar Converter for EDB has features such as automatic mailbox matching, parallel export, and priority exports to facilitate and speed up the process.

FAQs

How to fix the “Migration Failed Due to Transient Failure” error?

This error is related to an issue with a particular mailbox where the virtual folders in the Search Folders mailbox are corrupted. In this case, you need to run the Outlook.exe application with the options to clean finders and clean views.

How to fix error SourceMailboxAlreadyBeingMovedTransientException?

This error means that there were previous move requests attempts of the mailbox which are still active. You need to remove these requests before proceeding.

How to fix error UpdateMovedMailboxPermanentException?

This error occurs when moving a mailbox from a local server. A possible solution is to disable the on-premises mailbox or increase the quota of the mailbox.

How to fix error TooManyMissingItemsPermanentException?

This error occurs when there are numerous bad items in the mailbox or the bad items quota has exceeded. A possible solution is to retry the move or increase the quota.

How to fix error MailboxIsNotInExpectedMDBPermanentException?

This error is related to hybrid system. This error means that the mailbox has failed over to another database during the remote move. In this case, you can remove the move request and try again.

How to fix error- FailureType: StoragePermanentException?

This error occurs when there are issues with the storage where the source mailbox is stored. This happens when the mailbox has reached the quota of the size or reached the maximum number of items from a mailbox folder. To fix the problem, you need to split the data on the source mailbox and retry the move.

Was this article helpful?

YES0

About The Author

Ravi Singh

Ravi Singh is a Senior Writer at Stellar®. He is an expert Tech Explainer, IoT enthusiast, and a passionate nerd with over 7 years of experience in technical writing. He writes about Microsoft Exchange, Microsoft 365, Email Migration, Linux, Windows, Mac, DIY Tech, and Smart Home. Ravi spends most of his weekends working with IoT (DIY Smart Home) devices and playing Overwatch. He is also a solo traveler who loves hiking and exploring new trails.