"Object has already been deleted or has not been completely created" error

Products

• VMware vCenter Server
• VMware vSphere ESXi

Issue/Introduction

This article provides steps to work around the issue when reverting to a snapshot in vCenter Server fails with This object has already been deleted or has not been completely created. error.

Symptoms:

• 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 vCenter Server logs, you see entries similar to:
  
  13421:[2011-03-08 09:50:53.257 02580 info 'App' opID=3DB842F7-0000013A] [VpxLRO] -- ERROR task-489263 -- vm-9273 -- vim.vm.Snapshot.revert: vmodl.fault.ManagedObjectNotFound:
  13422-Result:
  13423-(vmodl.fault.ManagedObjectNotFound) {
  13424- dynamicType = <unset>,
  13425- faultCause = (vmodl.MethodFault) null,
  13426: obj = 'vim.vm.Snapshot:snapshot-133808',
  13427- msg = "",
   
• In ESX logs, you see entries similar to:
   
  [2011-03-08 09:50:47.127 F4F51B90 info 'Vmomi'] Throw vmodl.fault.ManagedObjectNotFound
  [2011-03-08 09:50:47.127 F4F51B90 info 'Vmomi'] Result:
  (vmodl.fault.ManagedObjectNotFound) {
  dynamicType = <unset>,
  faultCause = (vmodl.MethodFault) null,
  obj = 'vim.vm.Snapshot:576-snapshot-4',
  msg = "",
  }

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment. 　
 

 

Environment

VMware vSphere ESXi 7.0.0
VMware vCenter Server 6.5.x
VMware vSphere ESXi 6.7
VMware vSphere ESXi 6.5
VMware vCenter Server 6.0.x
VMware vSphere ESXi 6.0
VMware vCenter Server 6.7.x
VMware vCenter Server 7.0.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 ESX host then restarting the vpxd service.

Resolution

1. Remove the virtual machine from the inventory and re-add.
2. Restart the revert operation within vCenter Server.
3. Log in to the ESXi host directly, and revert the snapshot.
4. Revert the snapshot using the command-line in the ESXi host.                                                                               
5. For more information, see Committing snapshots from within the Service Console

Note: If your problem still exists after trying the steps in this article:

• Gather the VMware Support Script Data. For more information, see Collecting diagnostic information in a VMware Virtual Infrastructure Environment
• File a support request with VMware Support and note this Knowledge Base article ID (1039326) in the problem description. For more information, see Creating and managing Broadcom support cases

Note: You may also receive this error while taking a snapshot. In this case, remove the virtual machine from the inventory and re-add as per Step 1.

Additional Information

Collecting diagnostic information in a VMware Virtual Infrastructure Environment
How to stop, start, or restart vCenter Server services