Error on VM : "Object has already been deleted or has not been completely created"

Products

• VMware vCenter Server
• VMware vSphere ESXi

Issue/Introduction

Error while migrating the VM or reverting a snapshot: "The object 'vim.VirtualMachine:vm-name' has already been deleted or has not been completely created"

• Reverting to a snapshot in vCenter Server fails with the error:
  
  This object has already been deleted or has not been completely created.
  
  
• Unable to power on or migrate a cloned virtual machine.
• In the location less /var/log/vmware/vpxd/vpxd.log in vCenter Server logs, you see entries similar to:
  
  'App' opID=********-0000####] [VpxLRO] -- ERROR task-48#### -- <vm-moid> -- vim.vm.Snapshot.revert: vmodl.fault.ManagedObjectNotFound:
-Result:
-(vmodl.fault.ManagedObjectNotFound) {
- dynamicType = <unset>,
-faultCause = (vmodl.MethodFault) null,
: obj = 'vim.vm.Snapshot:<snapshot-moid>',
- msg = "",
  
  
• /var/run/log/hostd.log on esxi host, you see entries similar to:
  
  info 'Vmomi'] Throw vmodl.fault.ManagedObjectNotFound
info 'Vmomi'] Result:
(vmodl.fault.ManagedObjectNotFound) {
dynamicType = <unset>,
faultCause = (vmodl.MethodFault) null,
obj = 'vim.vm.Snapshot:<snapshot-moid>',
msg = "",
}

Environment

• VMware vCenter Server 7.x
• VMware vCenter Server 8.x
• VMware ESXi Server 7.x
• VMware ESXi Server 8.x

Cause

• This issue occurs due to a mismatched snapshot object id in vCenter Server database.
• The mismatch can be triggered by migrating the powered off virtual machine to a different ESXi host then restarting the vpxd service.

Resolution

1. Restart hostd and vpxa service on the ESXi host where the problematic VM is residing .
2. Re-register the VM