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(179.20000000000002, 65%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EG%3C/text%3E%3C/svg%3E)
Hello,
Since a week our mailbox migration jobs won't complete anymore.
After a while they end with an error as seen below...
Status
Data migrated:
Migration rate:
Error: TimeoutErrorTransientException: The call to 'https://mydomain/EWS/mrsproxy.svc' timed out. Error details: The request channel timed out attempting to send after 00:00:00.0049846. 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://mydomain/EWS/mrsproxy.svc' has exceeded the allotted timeout of 00:00:00.0049846. 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.0049846. 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://mydomain/EWS/mrsproxy.svc' has exceeded the allotted timeout of 00:00:00.0049846. The time allotted to this operation may have been a portion of a longer timeout.
Notice that tiny timeout. that's half a milisecond which seems ridiculous low.
Strange thing is that I can access the EWS page from external without any problems and I get the same page as the last screenshot on this page.
https://www.codetwo.com/kb/how-to-find-ews-url/
I tried disabling en re-abling the proxy with the commands below just to be sure:
Get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory -MRSProxyEnabled $false
Get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory -MRSProxyEnabled $true
I removed the end point and when creating it with the checkbox ticked to verify it it hang at creating.
With the checkbox unticked it created right away but it still doesn't seem to work.
What else can I check to get this working again? (it used to work fine for 2+ years but sometime this error showed up and then I just had to restart the sync or worst case delete the migration task and recreate it)
![](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(70.4, 18%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENM%3C/text%3E%3C/svg%3E)
Hi @GVB,
According to the information above, you could refer to the followings:
You can refer scenario 1 in the document for more information: Troubleshooting Hybrid Migration Endpoints in Classic and Modern Hybrid - Microsoft Community Hub
I figured out yesterday that the exchange server auth certificate expired on the 7th of April.
I renewed it by following this guide
https://www.alitajran.com/renew-microsoft-exchange-server-auth-certificate/
and now in the migration job the data consistency of 1 mailbox changed to Perfect but the sync counters ramain on 0.
the only thing I didn't do yet is going through the hybrid migration config again.
The migration job has this log. It seems it can connect fine as it can read out my local server name and the folder structure.
I'll go through the link you posted aswell. thanks for that.
4/25/2024 6:26:43 PM [xxxxxxx] 'MigrationService (on behalf of 'x@x.xx')' created request.
4/25/2024 6:27:19 PM [yyyyyyy] The Microsoft Exchange Mailbox Replication service 'yyyyyyy.EURP193.PROD.OUTLOOK.COM' (15.20.7472.44 ServerCaps:FFFFFFFF, ProxyCaps:07FFFFFFFFFFFFFFC7DD2DFDBF5FFFFFCB07EFFF, MailboxCaps:, legacyCaps:FFFFFFFF) is examining the request.
4/25/2024 6:27:19 PM [yyyyyyy] Resource information was found with reservation.
4/25/2024 6:27:19 PM [yyyyyyy] Content from the Shard mailbox (Mailbox Guid: c200852e-44bb-449e-8f6a, Database: 4c604971-8b84-4ad0-8097) will be merged into the target mailbox.
4/25/2024 6:27:19 PM [yyyyyyy] Connected to target mailbox 'domain.onmicrosoft.com\453458f1-d1f2-441a-ba51 (Primary)', database 'EURP193DG156-xxxxxx', Mailbox server 'yyyyyyy.EURP193.PROD.OUTLOOK.COM' Version 15.20 (Build 7472.0).
4/25/2024 6:27:22 PM [yyyyyyy] Connected to source mailbox 'domain.onmicrosoft.com\453458f1-d1f2-441a-ba51 (Primary)', database 'Mailbox Database 0490xxxxxx', Mailbox server 'SERVER-EXCH.domain.local' Version 15.1 (Build 2507.0), proxy server 'SERVER-EXCH.domain.local' 15.1.2507.23 ServerCaps:, ProxyCaps:, MailboxCaps:, legacyCaps:0FFD6FFFBF5FFFFFCB07FFFF.
4/25/2024 6:27:23 PM [yyyyyyy] Request processing started.
4/25/2024 6:27:23 PM [yyyyyyy] Source mailbox information:
Regular Items: 21, 54.22 KB (55,524 bytes)
Regular Deleted Items: 0, 0 B (0 bytes)
FAI Items: 0, 0 B (0 bytes)
FAI Deleted Items: 0, 0 B (0 bytes)
System Items: 0, 0 B (0 bytes)
4/25/2024 6:27:23 PM [yyyyyyy] Cleared sync state for request 453458f1-d1f2-441a-ba51 due to 'CleanupOrphanedMailbox'.
4/25/2024 6:27:23 PM [yyyyyyy] Mailbox signature will not be preserved for mailbox 'domain.onmicrosoft.com\453458f1-d1f2-441a-ba51 (Primary)'. Outlook clients will need to restart to access the moved mailbox.
4/25/2024 6:27:26 PM [yyyyyyy] Stage: CreatingFolderHierarchy. Percent complete: 10.
4/25/2024 6:27:27 PM [yyyyyyy] Initializing folder hierarchy from mailbox 'domain.onmicrosoft.com\453458f1-d1f2-441a-ba51 (Primary)': 72 folders total, 0 folders skipped.
4/25/2024 6:28:26 PM [yyyyyyy] Stage: CreatingFolderHierarchy. Percent complete: 10.
4/25/2024 6:28:26 PM [yyyyyyy] Transient error TimeoutErrorTransientException has occurred. The system will retry (1/60, 1/600).
4/25/2024 6:28:56 PM [yyyyyyy] The Microsoft Exchange Mailbox Replication service 'yyyyyyy.EURP193.PROD.OUTLOOK.COM' (15.20.7472.44 ServerCaps:FFFFFFFF, ProxyCaps:07FFFFFFFFFFFFFFC7DD2DFDBF5FFFFFCB07EFFF, MailboxCaps:, legacyCaps:FFFFFFFF) is examining the request.
4/25/2024 6:28:56 PM [yyyyyyy] Resource information was found with reservation.
4/25/2024 6:28:56 PM [yyyyyyy] Content from the Shard mailbox (Mailbox Guid: c200852e-44bb-449e-8f6a, Database: 4c604971-8b84-4ad0-8097-70377bfd39fb) will be merged into the target mailbox.
4/25/2024 6:28:56 PM [yyyyyyy] Connected to target mailbox 'domain.onmicrosoft.com\453458f1-d1f2-441a-ba51 (Primary)', database 'EURP193DG156-xxxxxx', Mailbox server 'yyyyyyy.EURP193.PROD.OUTLOOK.COM' Version 15.20 (Build 7472.0).
Hi,
As you said, “now in the migration job the data consistency of 1 mailbox changed to Perfect but the sync counters remain on 0”, did you mean the Timeout Error mentioned above has been solved? If the migration is now working successfully?
If so, I am glad to know that the issue has been resolved and the answer helps you, please click "Accept Answer" and kindly upvote it. If you have any questions, please let me know. Looking forward to your update.
No it's not working at all.
I tried running the migration wizard with only the OAuth option selected.
Then I did the OAuth & end points.
No error or anything but it's still not working.
The migration mailbox log gives this
4/29/2024 5:12:27 PM [DB7P193MB0345] The Microsoft Exchange Mailbox Replication service 'DB7P193MB0345.EURP193.PROD.OUTLOOK.COM' (15.20.7519.31 ServerCaps:FFFFFFFF, ProxyCaps:0FFFFFFFFFFFFFFFC7DD2DFDBF5FFFFFCB07EFFF, MailboxCaps:, legacyCaps:FFFFFFFF) is examining the request.
4/29/2024 5:12:27 PM [DB7P193MB0345] Resource information was found with reservation.
4/29/2024 5:12:27 PM [DB7P193MB0345] Content from the Shard mailbox (Mailbox Guid: c200852e-44bb-449e-8f6a-8ca01da547bb, Database: 4c604971-8b84-4ad0-8097-70377bfd39fb) will be merged into the target mailbox.
4/29/2024 5:12:27 PM [DB7P193MB0345] Connected to target mailbox 'mydomain.onmicrosoft.com\453458f1-d1f2-441a-ba51-76fa174f807e (Primary)', database 'EURP193DG022-db024', Mailbox server 'DB7P193MB0345.EURP193.PROD.OUTLOOK.COM' Version 15.20 (Build 7519.0).
4/29/2024 5:13:07 PM [DB7P193MB0345] Transient error EndpointNotFoundTransientException has occurred. The system will retry (3/60, 3/600).
Good news.
After an iisreset and full reboot of the local exchange I noticed that the counters on 1 mailbox jumped from 0 to 158.
I tried resuming, stopping and restarting but it didn't go on finishing the rest.
After stopping the batch and removing the 2 mailboxes I created a new batch job with 1 mailbox.
That completed within 5 minutes.
The other one also completed after adding it.
Port 443 ends on an apache which proxies to the exchange based on the domain name. I noticed a lot of proxy errors of incomplete/malformed request. those are gone too.
So it's not sure if I solved it or that it was something on microsoft's side that freaked out.
It looks like the migration is working. Glad to know the issue is solved and thanks for sharing your experience.
Please don't forget to mark it as answer, this will be easy for other community members to find the useful one and help more people with similar problems.
Thanks for understanding.
Just checking in to see if above information was helpful.
If the issue has been resolved, please mark the helpful replies as answers.
We did a few more and it's freaking out again.
The sync counters increase but then it hangs again.
One job had 100% synched status for several hours now.
In the log it's full of lines that it can't do the cleanup of the mailbox due to timeouts.
5/6/2024 10:43:06 AM [DB7P193MB0299] Failed to cleanup the source mailbox 'Blijdorp.onmicrosoft.com\660ecbc1-3c94-4553-aaa2-df0e4e563c43 (Primary)' after the move. Attempt 95/480. Error: TimeoutErrorTransientException.
5/6/2024 10:43:06 AM [DB7P193MB0299] Post-move cleanup failed. Remaining cleanup: SourceMailboxCleanup. The operation will try again in 30 seconds (96/480).
Hi,
According to your description, the reason could be failed to convert the source mailbox into a remote mailbox. This could make there are 2 mailboxes for the same user (one on-premises and a migrated one in the cloud).
To fix this, you could try manually disable the mailbox on-premises and convert it into a remote mailbox. You could follow the steps of How to recover when a mailbox exists in both Exchange Online and on-premises - Exchange | Microsoft Learn.
For more information, please refer to the document What to do if a migration is Completed With Warnings - Microsoft Community Hub.
That job with the cleanup error finally completed somewhere last night.
The other 2 now fail with the error below.
According to posts on the internet it's wrong credentials but I haven't touch those.
Error details: The HTTP request is unauthorized with client authentication scheme 'Negotiate'. The authentication
header received from the server was 'Negotiate,NTLM'. --> The remote server returned an error: (401) Unauthorized.. --> The HTTP request is unauthorized with client authentication scheme
'Negotiate'. The authentication header received from the server was 'Negotiate,NTLM'. --> The remote server returned an error: (401) Unauthorized.
this is a double post because my first one didn't appears for some reason until I posted it a second time.
Hi,
First of all, I would like to share with you that it is better for us to have one post with one problem or relevant information, if you have a new problem, we suggest that you can post a new thread to service better with your new problem.
However, there are some ways I suggest you could try according to your description.
Also, you could try to migrate by PST file since there are only 2 mailboxes cannot work.
Just checking in to see if above information was helpful.
If the issue has been resolved, please mark the helpful replies as answers.
We still experience problems.
Migrations jobs constantly fail and suddenly it completes without changing or restarting anything on our end.
It appears to be a common problem as I found several posts about this issue but never a solution to solve it so I guess it's something on microsoft's end that's freaking out.
Hi,
I am glad to know the migrations job is completed.
Since the issue disappears now and it is hard to reproducible, we cannot further investigate it. As you said, we also consider it is related to Microsoft. Meanwhile, we will report the issue to the Microsoft, hope they will fix it as soon as possible.
If my reply is helpful to you, you could mark the helpful replies as answers, this will help other community members for reference.
If there is anything else we can do for you, please feel free to inform us.
Just checking in to see if above information was helpful.
If the issue has been resolved, please mark the helpful replies as answers.
Things went fine for 1.5 months. Sometimes a mailbox migration took less than 5 minutes which is great.
Now migration jobs won’t work again since last Friday.
Even the data consistency value doesn’t update.
The usual useless error appears after hours in the job.
Error: TimeoutErrorTransientException: The call to 'https://mail.mydomain.com/EWS/mrsproxy.svc' timed out. Error details: The request channel timed out attempting to send after 00:00:00.0001606. 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://mail.mydomain.com/EWS/mrsproxy.svc' has exceeded the allotted timeout of 00:00:00.0001606. 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.0001606. 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://mail.mydomain.com/EWS/mrsproxy.svc' has exceeded the allotted timeout of 00:00:00.0001606. The time allotted to this operation may have been a portion of a longer timeout.
I already tried everything I tried before (recreating end point, restarting iis, all exchange services, full server reboot, restarting/deleting/recreating migration jobs and an actual and dummy user, restarting the web proxy) but it doesn’t move at all.
from external I can access the /EWS/exchange.asmx page without problems tho.
the /EWS/mrsproxy.svc doesn't show anything at all but I don't know if that's normal when nothing is posted to it.