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
    2017-01-01T20:33:06+00:00

    Hi Robert

    i am still getting the error and the 600 retry atttempt message again.  Is there anything else you need me to check?

    Martin

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-01-01T08:13:15+00:00

    Hi Martin,

    Thanks for the updates.

    I'd like to confirm whether the affected mailboxes are actually moved besides getting the error message.

    Regards,

    Robert

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-12-31T09:31:07+00:00

    Hi Larry

    i have checked a couple of other accounts (as well as the new account I created as per above) and they have no safe or blocked senders in them.

    as mentioned previously I can't even move a brand new account to O 365

    Martin

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-12-30T14:11:38+00:00

    Hi Martin,

    Thanks for your reply.

    Since the cause of this issue may be because there are blocked/safe senders in any user account of the affected users, please make sure every affected user doesn’t have any blocked/safe senders but not only one of them. We can investigate it further after getting the result, your efforts will be appreciated.

    Regards,

    Larry

    Was this answer helpful?

    0 comments
  5. Anonymous
    2016-12-30T01:50:38+00:00

    Hi Robert,

    One of the affected users does not have any blocked senders or safe senders in Outlook Web App

    So far all mailboxes I have tried are affected, including a brand new one i created before Christmas.

    Thanks

    Martin

    Was this answer helpful?

    0 comments