2 votesM.A. commented
For anyone else landing here with the same issue, it's a Server 2019 bug when using the same server for the migration job and the destination. The workaround is to use a second 2019 server as the management server, pointing to your separate destination server. The validation then passes.