CompletedWithErrors without details for mailbox migration batches in Exchange Server 2019 and 2016

In a Microsoft Exchange Server 2019 or Exchange Server 2016 environment, in case that different Domain Controllers (DCs) for global catalog (GC) and writeable DC session are used, when you create a migration batch for mailboxes, the migration batch fails with status CompletedWithErrors without further information in the Reports.

Migration batch failure is reported due to the ManagementObjectNotFound exception thrown from the Get-MoveRequestStatistics cmdlet that's called from the MsExchangeServiceHost service running in background. After the exception is thrown, the service executes Get-MoveRequestStatistics again and the command succeeds without any exception during retry. But the migration user is still marked as CompletedWithWarnings due to earlier exception.