New Exchange Online Migration-Batches fail with a CommunicationErrorPermanentException

Grenz, Sebastian 35 Reputation points
2023-07-21T15:51:17.7633333+00:00

Hi there,

we`re currently running an Exchange-Hybrid Setup and are in the process of moving our on-prem users to the cloud.

The first Migration-batches worked flawlessly. Since yesterday we are encountering problems with every new migration. The following errormessage occurs on every new batch:

CommunicationErrorPermanentException: The call to 'System.ServiceModel.Description.ServiceEndpoint' failed. Error details: The formatter threw an exception while trying to deserialize the message: There was an error while trying to deserialize parameter http://tempuri.org/:GetDatabaseForProvisioningResult. The InnerException message was ''Element' 'executingUserOrganization' from namespace 'http://schemas.datacontract.org/2004/07/Microsoft.Exchange.Data.Directory' is not expected. Expecting element 'dnWithoutRdn'.'. Please see InnerException for more details. --> 'Element' 'executingUserOrganization' from namespace 'http://schemas.datacontract.org/2004/07/Microsoft.Exchange.Data.Directory' is not expected. Expecting element 'dnWithoutRdn'.. --> The formatter threw an exception while trying to deserialize the message: There was an error while trying to deserialize parameter http://tempuri.org/:GetDatabaseForProvisioningResult. The InnerException message was ''Element' 'executingUserOrganization' from namespace 'http://schemas.datacontract.org/2004/07/Microsoft.Exchange.Data.Directory' is not expected. Expecting element 'dnWithoutRdn'.'. Please see InnerException for more details. --> 'Element' 'executingUserOrganization' from namespace 'http://schemas.datacontract.org/2004/07/Microsoft.Exchange.Data.Directory' is not expected. Expecting element 'dnWithoutRdn'. How can we troubleshoot this?

Kind regards,

Sebastian

Microsoft 365
Microsoft 365
Formerly Office 365, is a line of subscription services offered by Microsoft which adds to and includes the Microsoft Office product line.
3,289 questions
Microsoft Exchange Online
Microsoft Exchange Hybrid Management
Microsoft Exchange Hybrid Management
Microsoft Exchange: Microsoft messaging and collaboration software.Hybrid Management: Organizing, handling, directing or controlling hybrid deployments.
1,772 questions
0 comments No comments
{count} vote

Accepted answer
  1. Steven Wickersheimer 95 Reputation points
    2023-07-25T07:21:46.35+00:00

    Hi together,

    we have found something.

    Try the following:

    Connect via Powershell to Exchange Online with the following command: "Connect-ExchangeOnline"

    Enter "Get-MoveRequest" and search for old Jobs.

    Deleted them (Remove-MoveRequest) and started a new MoveRequest (New-MoveRequest / https://www.alitajran.com/move-mailbox-to-exchange-online-with-powershell/).

    At the moment copy of one user is running :)

    4 people found this answer helpful.

6 additional answers

Sort by: Most helpful
  1. 2023-07-24T13:43:12.2566667+00:00

    Same problem here since Thursday last week. I was able to migrate 4 mailboxes yesterday. The same issue is back today and I can't continue with the migration

    0 comments No comments

  2. Grenz, Sebastian 35 Reputation points
    2023-07-24T18:55:43.46+00:00

    Just to add to @Klarner, Steffen | SmartWork IT GmbH response. Our last successfull migration was last Thursday as well. 2 Migration Batches (each with only one user), which were created just 4 minutes apart, from which only the "first" one succeeded.

    It doest not matter which database the user is currently on, which server, if its an old or new user or if its "just" a shared mailbox. All of these migrations result in the same error message posted above.

    The generated XML from the Migrationbatch Diagnostic does not give any more hinbts than what was posted in my first question...

    Kind regards,

    Sebastian

    0 comments No comments

  3. RevelinoB 2,215 Reputation points
    2023-07-22T10:50:09.95+00:00

    Hello Sebastian,

    I noticed you encountered issues during the migration of users to the cloud in an Exchange-Hybrid setup, this can be frustrating, but there are some steps you can take to troubleshoot and resolve the problem. The error message you provided indicates that there is a deserialization issue related to the 'executingUserOrganization' element in the Microsoft Exchange Data Directory.

    Here are some steps you can follow to troubleshoot this issue:

    • Check Network Connectivity: Ensure that there are no network connectivity issues between your on-premises Exchange server and the Exchange Online service. Verify that the required ports are open and that there are no firewalls or proxies blocking the communication.
    • Check Service Status: Verify the service status of Exchange Online to ensure that there are no ongoing service outages or disruptions that might be causing the issue. You can check the Microsoft 365 Service Health Dashboard or the Exchange Online Service Health page for any reported incidents. Check Permissions: Ensure that the account you are using for migration has the necessary permissions to access and modify user attributes in both on-premises Exchange and Exchange Online. The account should have the required roles, such as Global Administrator or Exchange Organization Management. Review Migration Settings: Double-check the migration batch settings to ensure that all parameters are correctly configured. Pay special attention to any custom settings and options that might be influencing the migration process. Verify Attributes: Check if there are any inconsistencies in the attributes of the user objects being migrated. Specifically, verify the 'executingUserOrganization' element in the Microsoft Exchange Data Directory and compare it with the expected format. Update Exchange Servers: Ensure that your on-premises Exchange servers are up-to-date with the latest cumulative updates and patches. Sometimes, migration issues can be caused by outdated software. Inspect Logs: Review the migration logs to identify any specific errors or warnings that might provide more context about the root cause of the issue. Logs are crucial in troubleshooting migration problems. Contact Microsoft Support: If the issue persists and you are unable to resolve it, don't hesitate to reach out to Microsoft Support for assistance. They can provide more in-depth analysis and help resolve complex migration issues.

    By following these steps, you should be able to identify and resolve the problem with your migration batches. Remember to document the troubleshooting process and any changes you make, as this can be helpful in case similar issues occur in the future. Good luck with your migration! If you have any more specific questions or encounter new information, feel free to ask for further assistance, thanks!


  4. Yuki Sun-MSFT 40,016 Reputation points
    2023-07-24T07:53:25.6666667+00:00

    Hi @Grenz, Sebastian

    The first Migration-batches worked flawlessly. Since yesterday we are encountering problems with every new migration. The following errormessage occurs on every new batch:

    Since it has been working flawlessly earlier, in case it was a transient backend issue which has already been restored, could you try it again and see how it goes?

    In case the error persists, it's also suggested to have a look at the Service Health dashboard via the M365 admin center to see if there's any potentially relevant issue there.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    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.