This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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 features that help users manage their subscriptions, account settings, and billing information.
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.
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?
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.
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
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.
Hi Robert
im back at work tomorrow so will run it again and will let you know
Martin