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(19.2, 46%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EIH%3C/text%3E%3C/svg%3E)
I installed Exchange 2019 RTM in coexistence with Exchange 2016 and moved some mailboxes for testing and everything was working fine. Last week I installed and updated Exchange 2019 CU 11 and after that the migration is not working and the mailboxes in the migration batch are in sync and there is no data transfer. I searched and found that Exchange Search and Exchange Search host controllers are inactive. Both services switched to automatic start but nothing happened and mailboxes are still in sync state.
Downloaded the user mailbox report and found these in the log file.
"Transient error BigFunnelTransientException has occurred. The system will retry (1/600).
[Server2] The Microsoft Exchange Mailbox Replication service 'Server2.com' (15.2.986.14 caps:3FFFFF) is examining the request.
[Server2] Connected to target mailbox '-a1db-aecb576f4467 (Primary)', database 'db01', Mailbox server 'Server2.com' Version 15.2 (Build 986.0).
[Server2] Connected to source mailbox '2-a1db-aecb576f4467 (Primary)', database 'db10', Mailbox server 'Server1.com' Version 15.1 (Build 2308.0), proxy server 'Server1.com' 15.1.2308.20 caps:0FFF5FFFFFCB07FFFF.
[Server2] Request processing continued, stage LoadingMessages.
[Server2] Stage: LoadingMessages. Percent complete: 20.
[Server2] Stage: LoadingMessages. Percent complete: 20."
Please assist
I want to confirm with you whether mailbox could be migrated successfully if you create a new mailbox on Exchange 2016 then migrate it to Exchange 2019?
If mailbox could be migrated successfully, try to delete existing batch migration request then create new one as AndyDavid suggested.
![](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(265.6, 25%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMJ%3C/text%3E%3C/svg%3E)
We too are experiencing this same issue migrating our mailboxes from exchange 2016 to 2019. Tried a single mailbox migration and transientfailure at 95%. Have read and tried everything I could find online to try and still not working......
I would remove the batch and start over.
I have tried created new batches and now this time error message has been changed. ****"StalledDueToTarget_DiskLatency"**** and no migration started.
Please suggest.
Here is some information about this new migrate request:
I would suggest you try to stop/delete all existing migration requests. Then try to migrate only one mailbox.
The issue still persist and contacted the vendor to replace the drives with high performance.
There is an update that after upgrading the server hardware the issue of disk latency during mailbox migration had gone and now StalledDueToTarget_MdbReplication is showing although mailbox are migrating.
Kindly assist.