none
Staged Migration to Office 365 - Migration Endpoint Error RRS feed

  • Question

  • I'm in the middle of a staged migration to Office 365 from on premise Exchange 2003.   We've successfully completed multiple batches but now the Migration Endpoint will not connect to the on prem server.  The Microsoft Remote Connectivity Analyzer comes back Green (output below).   I've verified the firewall is not getting in the way.  I've double checked all the settings and they are correct (and are the same settings that had been working fine for more than 20 migration batches).   Now when I try to use the endpoint I get an error:

    error
    We weren't able to connect to the remote server. Please verify that the migration endpoint settings are correct and your certificate is valid, and then try again. Consider using the Exchange Remote Connectivity Analyzer (https://testexchangeconnectivity.com) to diagnose the connectivity issues.

    The remote connectivity analyzer comes back green (warnings are related to compatibility with Windows Phone devices, which I don't care about it here)

    When I open the IIS logs on the server I can see Microsoft's cloud service connecting but then nothing else.  There are no errors or warnings in the event log on the activesync server or on the domain controllers.   

    2019-06-02 12:10:16 W3SVC1 FS1 192.168.1.8 RPC_IN_DATA /rpc/rpcproxy.dll fs1.SOMEDOMAIN.com:6002 443 - 40.97.127.77 MSRPC - webmail.SOMEDOMAIN.com 501 0 0 15
    2019-06-02 12:10:16 W3SVC1 FS1 192.168.1.8 RPC_OUT_DATA /rpc/rpcproxy.dll fs1.SOMEDOMAIN.com:6002 443 - 40.97.127.77 MSRPC - webmail.SOMEDOMAIN.com 501 0 0 0
    2019-06-02 12:10:20 W3SVC1 FS1 192.168.1.8 RPC_IN_DATA /rpc/rpcproxy.dll fs1.SOMEDOMAIN.com:6002 443 - 40.97.127.77 MSRPC - webmail.SOMEDOMAIN.com 501 0 0 0
    2019-06-02 12:10:20 W3SVC1 FS1 192.168.1.8 RPC_OUT_DATA /rpc/rpcproxy.dll fs1.SOMEDOMAIN.com:6002 443 - 40.97.127.77 MSRPC - webmail.SOMEDOMAIN.com 501 0 0 0
    2019-06-02 12:10:21 W3SVC1 FS1 192.168.1.8 RPC_IN_DATA /rpc/rpcproxy.dll BN6PR1401MB2097.namprd14.prod.outlook.com:6002 443 - 40.97.127.77 MSRPC - webmail.SOMEDOMAIN.com 501 0 0 0
    2019-06-02 12:10:21 W3SVC1 FS1 192.168.1.8 RPC_OUT_DATA /rpc/rpcproxy.dll BN6PR1401MB2097.namprd14.prod.outlook.com:6002 443 - 40.97.127.77 MSRPC - webmail.SOMEDOMAIN.com 501 0 0 0
    2019-06-02 12:10:26 W3SVC1 FS1 192.168.1.8 RPC_IN_DATA /rpc/rpcproxy.dll BN6PR1401MB2097.namprd14.prod.outlook.com:6002 443 - 40.97.127.77 MSRPC - webmail.SOMEDOMAIN.com 501 0 0 0
    2019-06-02 12:10:26 W3SVC1 FS1 192.168.1.8 RPC_OUT_DATA /rpc/rpcproxy.dll BN6PR1401MB2097.namprd14.prod.outlook.com:6002 443 - 40.97.127.77 MSRPC - webmail.SOMEDOMAIN.com 501 0 0 0

    Any ideas for further troubleshooting for this?  I'm stuck.  Any advice would be most appreciated.



    Sunday, June 2, 2019 3:33 PM

All replies

  • Your test is hardly definitive since it's testing ActiveSync while mailbox migration endpoint uses Exchange Web Services.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Sunday, June 2, 2019 8:56 PM
    Moderator
  • This is Exchange Server 2003.  If I'm not mistaken, EWS didn't come in until Exchange 2007 or 2010?
    Sunday, June 2, 2019 11:28 PM
  • So you're doing an IMAP migration?  That's still not ActiveSync.

    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Celebrating 20 years of providing Exchange peer support!

    Monday, June 3, 2019 2:47 AM
    Moderator