Migration to Office 365 Failed - CommunicationErrorTransientException at 95%

Anonymous
2016-12-14T08:02:15+00:00

Hello

I am working with a client to the point where they can move their mailboxes to Office 365 themselves.   I am having some issues - the synch works fine but when it comes to finalising i keep getting this error over and over again

FailureType       : CommunicationErrorTransientException

FailureHash       : 19cc

FailureCode       : -2146233088

MapiLowLevelError : 0

FailureSide       : Source

FailureSideInt    : 1

ExceptionTypes    : {Exchange, Transient}

ExceptionTypesInt : {1, 2}

Message           : The call to 'https://smtp.mmca.co.nz/EWS/mrsproxy.svc mmexchange.mmca.local (14.3.227.0

                    caps:05FFFF)' failed. Error details: The remote endpoint no longer recognizes this sequence. This

                    is most likely due to an abort on the remote endpoint. The value of wsrm:Identifier is not a known

                    Sequence identifier. The reliable session was faulted.. --> The remote endpoint no longer

                    recognizes this sequence. This is most likely due to an abort on the remote endpoint. The value of

                    wsrm:Identifier is not a known Sequence identifier. The reliable session was faulted.

My set up is 1 Exchange 2010 server.

Microsoft 365 and Office | Subscription, account, billing | For business | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

52 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2016-12-15T08:19:14+00:00

    Hi Martin,

    I’d like to confirm some information to better understand the issue:

    1. What migration did you perform, IMAP, staged, Cutover or hybrid migration?
    2. Connect PowerShell to Exchange Online: https://technet.microsoft.com/library/jj984289(v=exchg.160).aspx 
    3. Run the following commands:

    Get-MigrationBatch | fl

    Get-MigrationStatistics | fl

    Get-MigrationUserStatistics -Identity user@domainom -IncludeReport | FL

    Note: user@domainom is the problematic user.

    To protect your privacy, I have sent a private message to request the PowerShell output. Please use this link to access the private message: 

    https://answers.microsoft.com/en-us/privatemessages/list

    Regards,

    Robert

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-12-18T21:39:52+00:00

    Hi Robert

    I sent through some information last week.  Did you receive it?

    Thanks

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-12-19T08:20:02+00:00

    Hi Martin,

    Sorry for the delay.

    Yes, I have received your information.

    To further troubleshoot the issue, can you please confirm whether you have configured any load balancer in your on-premises server? If yes, please temporarily bypass it and do the migration again to test the issue.

    Regards,

    Robert

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-12-19T08:38:07+00:00

    Hi Robert

    There is no load balancer in use at all.

    Thanks

    Martin

    Was this answer helpful?

    0 comments
  5. Anonymous
    2016-12-20T10:29:06+00:00

    Hi Martin,

    Thanks for the updates.

    I have tested your URL https://smtp.mmca.co.nz and found it cannot be accessed externally. I'd like to confirm whether you have manually changed that.

    Meanwhile, do you have the specific users that are not moved to Office 365? If yes, please run the command Get-MigrationUserStatistics -Identity user@domainom -IncludeReport | FL for them and send me the results through private message.

    Thanks,

    Robert

    Was this answer helpful?

    0 comments