After updating Exchange 2019 CU11 migration from Exchange 2016 stopped

Innocent Heartvoice 286 Reputation points
2022-03-21T05:11:53.433+00:00

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

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,408 questions
{count} votes

4 answers

Sort by: Most helpful
  1. Andy David - MVP 142.8K Reputation points MVP
    2022-03-21T11:57:41.493+00:00

    I would remove the batch and start over.

    0 comments No comments

  2. Innocent Heartvoice 286 Reputation points
    2022-03-24T09:40:54.267+00:00

    I have tried created new batches and now this time error message has been changed. ****"StalledDueToTarget_DiskLatency"**** and no migration started.

    Please suggest.


  3. Innocent Heartvoice 286 Reputation points
    2022-04-18T04:35:13.343+00:00

    The issue still persist and contacted the vendor to replace the drives with high performance.

    0 comments No comments

  4. Innocent Heartvoice 286 Reputation points
    2022-04-20T08:40:18.937+00:00

    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.

    0 comments No comments