Views:
The issue is because of the VM losing connection to the vCenter, thus, both DSM and DSVA cannot communicate with the VM.
To resolve the issue, the vCenter Administrator should remove the VM from the vCenter Inventory, and then add it back to force the VM build connection to the vCenter.
Note: There are times that administrator renames the VM, but the VM’s folder name in the datastore is still the original name when the VM was created. Thus, the administrator should take note of the VM's folder name in the datastore before proceeding.