I'm getting this error: The connection to the server 'ews.contoso.com' could not be completed. ---> Microsoft.Exchange.MailboxReplicationService.RemoteTransientException: The call to 'https://ews.contoso.com/EWS/mrsproxy.svc' failed. Error details: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. --> The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.. ---> Microsoft.Exchange.MailboxReplicationService.RemotePermanentException: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. ---> Microsoft.Exchange.MailboxReplicationService.RemotePermanentException: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.
Nothing on Google helps at all! I put in a call to Office 365 support and the tech was actually worse than not helpful about this issue. At the start he mentioned that I would likely need to pay for a support ticket to get Exchange support. He then gave me 'best effort' support which included telling me to change all of my EWS virtual directory authentication to basic from Integrated Windows authentication, which of course Exchange warns will break Outlook Anywhere. That didn't fix it. His suggestion was to export to PST, delete the whole AD account for the user, create a new AD account with all the same user information, create a new local mailbox, and finally import the PST.
I have Exchange 2013 and Exchange 2016 in my org. They are behind a hardware load balancer. I have recreated the Migration Endpoint in Office 365 to no avail. Migrations were fine earlier this week. They are now broken. I have put the HLB into maintenance mode for two servers and I am only using one server to connect with for EWS hoping that would eliminate any persistence issues. I changed the timeout value from the working fine before 60 seconds to now still not working 600 seconds.
I now have an open paid Exchange support ticket with Microsoft. I will update this with findings/results.
On Prem Exchange support said it was an Office 365 issue. After a week migrations just started working again. No changes were made by me.
No comments:
Post a Comment