Please refer to the KB article VMware Knowledge Base. It appears to be a similar issue.
As per this KB, the workaround is as follows
- From the vSphere Web Client select an affected Virtual Machine and click Launch Remote console. Once it is loaded, close the session
- Run the migration again.
Thanks