Search the VMware Knowledge Base (KB)
Products:
View by Article ID

"Object has already been deleted or has not been completely created" error (1039326)

  • 8 Ratings
Language Editions

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.  

 

Purpose

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.

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

This is a known issue affecting vSphere 4.x.

Currently, there is no resolution.
 
To work around this issue:
  1. Remove the virtual machine from the inventory and re-add.
  2. Restart the revert operation within vCenter Server.
  3. Log in to the ESX/ESXi host directly using the vSphere Client, and revert the snapshot.
  4. Revert the snapshot using the command-line in the ESX or ESXi host. For more information, see Committing snapshots on ESX/ESXi host from command line (1026380).
  5. Restart the vCenter Server service. For more information, see Stopping, starting, or restarting vCenter services (1003895)
Note: If your problem still exists after trying the steps in this article:
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.

Tags

revert-snapshot-fails take-snapshot-fails

See Also

Update History

05/23/2012 - Added additional resolution step. 07/11/2013 - Added additional symptom

Language Editions

ja,2077163;

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 8 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 8 Ratings
Actions
KB: