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-22T20:17:14+00:00

    Hi Robert,

    Sorry for being so vague - my mailboxes are all in Exchange 2010 which is also configured as the hybrid server.  I am trying to remote move the mailboxes to Office 365.

    Here are the URLs for the EWS

    [PS] C:\Windows\system32>Get-WebServicesVirtualDirectory | select name,*URL*|fl

    Creating a new session for implicit remoting of "Get-WebServicesVirtualDirectory" command...

    Name                 : EWS (Default Web Site)

    InternalNLBBypassUrl : https://mmexchange.mmca.local/ews/exchange.asmx

    InternalUrl          : https://smtp.mmca.co.nz/EWS/Exchange.asmx

    ExternalUrl          : https://smtp.mmca.co.nz/EWS/Exchange.asmx

    Thanks

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-12-22T09:31:49+00:00

    Hi Martin,

    Thanks for the information.

    Yes, I know the url is linked to an IIS interface, but it is not right. Normally, the mrsproxy url should be something like mail.contoso.com and it should lead to the online mail sign-in page.

    Given the situation, please go to your EAC in your Exchange server, navigate to servers – virtual directories – EWS, send us a screenshot for the internal and external url.

    Meanwhile, by saying “My set up is 1 Exchange 2010 server.”, do you mean your mailboxes are in Exchange server 2010? I’d like to confirm where your hybrid server is deployed, in Exchange 2010 or 2013.

    Thanks,

    Robert

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-12-21T01:58:00+00:00

    Hi Robert,

    I can access https://smtp.mmca.co.nz fine from 2 different internet connections.  I get an IIS7 splash screen.

    I will flick through that other thing via PM>

    Thanks

    Martin

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-12-20T10:29:06+00:00

    Hi Martin,

    Thanks for the updates.

    I have tested your URL https://smtp.mmca.co.nz and found it cannot be accessed externally. I'd like to confirm whether you have manually changed that.

    Meanwhile, do you have the specific users that are not moved to Office 365? If yes, please run the command Get-MigrationUserStatistics -Identity user@domainom -IncludeReport | FL for them and send me the results through private message.

    Thanks,

    Robert

    Was this answer helpful?

    0 comments
  5. Anonymous
    2016-12-19T08:38:07+00:00

    Hi Robert

    There is no load balancer in use at all.

    Thanks

    Martin

    Was this answer helpful?

    0 comments