MoveRequest and MailboxExportRequest hangs in Queued/WaitingForJobPickup status

Kenny M 1 Reputation point
2022-06-20T12:11:37.13+00:00

TwoExchange 2019 CU12 May22SU servers running in a DAG with 4 databases, 2 copies on each. I am not able to perform neither MoveRequest og MailboxExportRequest, as all tasks are just stuck in Queue/WaitingForJobPickup. I am running out of ideas for reasons for this. I have tried the following:

  • Rebooted both servers
  • Resources looks fine: CPU, memory and disk space
  • No CopyQueueLength/ReplayQueueLength
  • All services are running
  • ServerComponentState looks fine
  • Test-ReplicationHealth looks fine
  • Turning off Windows Firewall on both servers

Where to go from here?

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,281 questions
0 comments No comments
{count} votes

4 answers

Sort by: Most helpful
  1. Aholic Liang-MSFT 13,666 Reputation points Microsoft Vendor
    2022-06-21T07:29:08.937+00:00

    Hi @KennyM-3958 ,

    Have you checked if the requests are still in the queue after the server has restarted?
    If they are still in the queue, please refer to the following cmdlets to remove them :

    Get-MailboxExportRequest –Status Queued | Remove-MailboxExportRequest  
    Get-MoveRequest  -MoveStatus InProgress | Remove-MoveRequest  
    

    Then please restart the ‘MSExchangeMailboxReplication’ service and create a new request to see if it changes.


    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.


  2. Andy David - MVP 139.8K Reputation points MVP
    2022-07-05T15:06:00.813+00:00

    Any anti-virus or other 3rd party software running on the server?


  3. Kenny M 1 Reputation point
    2022-11-25T12:40:14.8+00:00

    I was never able to solve this issue. I ended up installing new Exchange servers and moving the database files and mounting them on the new Exchange servers.

    So it was either something specific for the DAG og the two existing servers.

    0 comments No comments

  4. Kenny M 1 Reputation point
    2022-12-20T11:23:02.293+00:00

    I'll be damned, I figured out the source of the issue today.

    I modified the values of the "MsExchangeMailboxReplication.exe.config" in order to speed up MoveRequests and ExportRequests. The config file actually states which values are valid:

      <!-- Mailbox Replication Service configuration   
        Setting Name - Default, MinValue, MaxValue  
        MaxActiveMovesPerSourceMDB - 20, 0, 100  
        MaxActiveMovesPerTargetMDB - 20, 0, 100  
    

    I set the value for both MaxActiveMovesPerSourceMDB and MaxActiveMovesPerTargetMDB to "200", which was outside the allowed range. After reducing both these to 100 and restarting the service, everything works again.