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 No comments

52 answers

Sort by: Oldest
  1. Anonymous
    2017-01-05T07:51:25+00:00

    Hi Martin,

    Sorry for the confusion.

    Yes, I mean the Hybrid Configuration Wizard.

    Thanks,

    Robert

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-01-08T06:26:49+00:00

    Hi Martin,

    Have you run the HCW and done the migration again?

    Regards,

    Robert

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2017-01-08T06:34:11+00:00

    Hi Robert

    im back at work tomorrow so will run it again and will let you know

    Martin

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2017-01-08T22:06:14+00:00

    Hi There

    Not sure if this is part of the issue, but in my Event Log I am getting the following errors on the Exchange server

    A process serving application pool 'MSExchangeServicesAppPool' failed to respond to a ping. The process id was '12472'.

    When I stop this app pool I get a timeout error when running the remote mailbox move.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2017-01-09T01:21:30+00:00

    Hi

    I have rerun the HCW again - no success I am afraid.  I am still getting the same error.

    The '

    A process serving application pool 'MSExchangeServicesAppPool' failed to respond to a ping. The process id was '7968' error appeared again in the event log.

    Martin

    Was this answer helpful?

    0 comments No comments