This issue may happen when the ExchangeGUID of the cloud MailUser doesn't match the ExchangeGUID of the on-premises mailbox.
Here is a KB about the issue you are encountering https://support.microsoft.com/en-us/help/3065754/the-remote-server-returned-an-error-404-or-http-request-has-exceeded-t. You can reset the cloud ExchangeGUID as suggested in the KB.
If the issue persists, you can try to filter the synced MailUser out, delete it from Office 365, and then sync it to the cloud again to migrate the on-premises for the test.
Error when Migrating on-prem mailbox to exchange online
Data migrated:
Migration rate:
Error: TimeoutErrorTransientException: The call to 'https://exsync.ssm.com.my/EWS/mrsproxy.svc' timed out.
Error details: The request channel timed out attempting to send after 00:00:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.
--> The HTTP request to 'https://exsync.ssm.com.my/EWS/mrsproxy.svc' has exceeded the allotted timeout of 00:00:00. The time allotted to this operation may have been a portion of a longer timeout.
--> The request channel timed out attempting to send after 00:00:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.
--> The HTTP request to 'https://exsync.ssm.com.my/EWS/mrsproxy.svc' has exceeded the allotted timeout of 00:00:00. The time allotted to this operation may have been a portion of a longer timeout.
Last successful sync date:
Data consistency score:
Please help me to solve this issue..
2 answers
Sort by: Most helpful
-
Amit Singh 5,071 Reputation points
2022-07-07T10:27:12.86+00:00 -
KyleXu-MSFT 26,291 Reputation points
2022-07-08T07:28:40.193+00:00 Are you using Exchange 2010? If so, have a check about "DataImportTimeout" in "C:\Program FIles\Microsoft\Exchange Server\v14\ClientAccess\exchweb\ews"
If you aren't using Exchange 2010, I would suggest you try to disable MRS proxy and enable it again:
Get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory -MRSProxyEnabled $false Get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory -MRSProxyEnabled $true
If could, I also suggest you try to disable firewall temporarily for check whether this issue caused by firewall configuraton.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.