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-09T09:26:08+00:00

    Hi Martin,

    Thanks for the updates.

    I’m not quite sure whether the error is related to the migration move. But before using other alternatives, please use PowerShell to do move to test if the issue persists.

    Here are the steps:

    1). $RemoteCredential= Get-Credential

    Then, type in the on-premise administrator credential in the prompt window.

    2). New-MoveRequest -Identity “an on-premise mailbox” -Remote -RemoteHostName “mail.domain.com” -TargetDeliveryDomain domain.mail.onmicrosoft.com -RemoteCredential $RemoteCredential

    Please note that the cmdlets above need to be run via the Exchange Online PowerShell.

    Regards,

    Robert

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-01-09T03:24:40+00:00

    Just another question

    what are my other alternatives to uploading to office 365 apart from PST migrations?  Would it be beneficial perhaps to have another Exchange 2013 server onsite, migrate to it and then migrate the mailboxes from Exchange 2013 to O365?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-01-09T03:18:01+00:00

    Hi

    I am now getting this error

    A process serving application pool 'MSExchangeServicesAppPool' suffered a fatal communication error with the Windows Process Activation Service. The process id was '11928'. The data field contains the error number.

    What is happening is that the w3wp.exe process is going into a suspended mode and therefore isn't finishing off the remote move.

    Was this answer helpful?

    0 comments
  4. 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
  5. 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