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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2016-12-29T23:43:18+00:00

    Hi Martin,

    Sorry for the delay.

    I would like to confirm whether you the affected users have set any blocked senders or safe senders in the Outlook client or Outlook Web App. If yes, please remove them all and run the migration again to test the issue.

    Meanwhile, I'd like to know how many mailboxes are affected.

    Regards,

    Robert

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-12-26T19:59:52+00:00

    Hi Martin,

    Thanks for the updates.

    I have sent consult emails to our relevant team. I will let you know once I get any updates. Thanks for your patience.

    Regards,

    Robert

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-12-26T10:00:16+00:00

    hi

    Sorry for the late reply - have been busy with Christmas

    There is a proxy server onsite but it is called mmsec.mmca.local and Internet Explorer is set not to use it at all.

    Thanks

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-12-25T19:53:40+00:00

    Hi Martin,

    Have you checked the last reply? Please let us know the updates when you have time.

    Regards,

    Robert

    Was this answer helpful?

    0 comments
  5. Anonymous
    2016-12-23T10:14:01+00:00

    Hi Martin,

    Thanks for the information in private message. From the report, I can see the connection to the source mailbox on your on-premises failed. There is a proxy server named mmexchange.domain.local in front of the Exchange server. Is it a network firewall in your internal environment? If yes, please check there is any rule that may block the IP addresses or Ports from Exchange Online. I suggest you try to bypass it and test the migration request again.

    Regards,

    Alex

    Was this answer helpful?

    0 comments