Skip to main content

 

Druva Documentation

VMware VMOMI errors

This topic provides a list of the VMware VMOMI errors that you may encounter while working with Phoenix.  VMOMI errors that you may encounter while working with Phoenix.  

VMWARE_VMOMI1

 If this error is displayed, perform the following steps to ensure there is no problem with the target virtual machine.

Manually take a snapshot using vSphere client or by web client with help of  following steps:

  • Unselect the snapshot virtual machine's memory option.
  • Select the Quiesce guest file system option if quiescing  is enabled on the Phoenix virtual machine backup policy. OR Unselect the Quiesce guest file system option if quiescing  is disabled on the Phoenix virtual machine backup policy.

Error Solution: 

 

Error Message: Snapshot of VM failed[Another snapshot of VM might be in the progress.]

Error Solution: Wait for the old snapshot to complete and trigger another backup/restore request.

 

Error Message: Snapshot of VM failed [The number of levels in the snapshot tree exceeds the supported maximum limit.]

Error Solution: Consolidate or delete the old snapshot and retry the operation.

 

Error Message: Snapshot of VM failed[The VM is in invalid state to take snapshot.]

Error Solution: To resolve the error:

  • If virtual machine is invalid or orphaned then a snapshot of such virtual machine not supported.
  • If current power state of virtual machine is not supported to take the snapshot. You can change the power state of virtual machine. (Power off/ Power on virtual machine) and retry the operation.

 

Error Message: Snapshot of VM failed[Incompatible device are present on VM.]

Error Solution: Change the SCSI Controller mode.

 

Error Message: Snapshot of VM failed[Permission to perform this operation was denied.]

Error Solution: Check for the privileges.

 

Error Message: Snapshot of VM failed[An error occurred while quiescing the virtual machine. Please retry the backup/restore again.]

Error Solution: Retry the operation.

 

Error Message: Snapshot of VM failed [Current license or ESXi version prohibits execution of the requested operation.]

Error Solution: Check the vCenter, ESXi version and the license details. You must use the version of  vCenter and ESXi that  are supported by Phoenix. For more                                                    information, see Support matrix.

 

VMWARE_VMOMI2

Error Message:  Reverting of snapshot Failed for VM[Another snapshot of VM might be in the progress]

Error Solution: Wait for the old snapshot to complete and trigger another backup/restore request.

 

Error Message: Reverting of snapshot Failed for VM[The VM is in invalid state.] 

Error Solution: If VM is invalid or orphaned then snapshot of such VM not supported.

 

Error Message:  Reverting of snapshot Failed for VM[Problem in VM configuration]

Error Solution: Check the virtual machine configuration and see client log for more information about which virtual machine configuration entity  caused the issue.

 

Error Message: Reverting of snapshot Failed for VM[Permission to perform this operation was denied.] 

Error Solution: Check required user privileges.

 

VMWARE_VMOMI3

Error Message: Problem with Datastore.[Problem with datastore <datastore_name>]  

Error Solution:  To resolve problems with data store:

  • Check if the data store is writable or not.
  • Check if data store is accessible from ESX host at the place of restore.

 

Error Message: Problem with Datastore[Move disk operation failed.]

Error Solution:  To resolve problems with the move disk operation:

  • Check if data store is writable.
  • Check is data store is accessible from ESX host, where you are trying to restore.
  • Rename or manually move the problematic disk.
  • In case of restore to alternate location, you can select other datastore

 

Error Message:  Problem with Datastore[Unable to locate the datastore [<datastore_name>]] 

Error Solution:  To resolve problems with locating data store:

  • Check whether mentioned data store is accessible from Vcenter or ESX.
  • In case of restore to an alternate location, select other data store.

 

Error Message: Cannot allocate memory (0xbad0014, Out of memory). 

Error Description: This error message is displayed in the vmware.log file.

Error Solution:  Migrate the virtual machine to another ESX.  For more information see,  Backing up the virtual machine fails when CBT is enabled .

VMWARE_VMOMI4

Error Message:  No disk space available [No disk space available to create new VM [Restore process required <required  free space in bytes> bytes free disk space,                                             <actual available free space in bytes>bytes free disk space  available on datastore <datastore name>.] OR

                                         No disk space available[No disk space available to create new VM[<vm_name>]].

Error Description: This error can occur if there is inadequate disk space on the data store to restore selected virtual machine.

Error Solution: To resolve the error:

  • Manually free some disk space on the data store and retry the operation. OR
  • Select some other data store with adequate disk space.

VMWARE_VMOMI5

Error Message: Create new operation failed[Host capability max supported VMs is exceeded]

Error Description: This error can occur if the ESX host has reached the maximum number of supported virtual machine and you are trying to add/create new virtual machine.

Error Solution: To resolve the error:

  • Delete atleast one virtual machine and retry the restore request. OR
  • Try to restore virtual machine to other ESX hosts.

 

VMWARE_VMOMI6

Error Message:  Delete snapshot failed for VM[The VM is in invalid state]

Error Solution: If the current power state of virtual machine does not support to delete the snapshot. Change power state of virtual machine. (power off the vm.)

 

Error Message: Delete snapshot failed for VM[The virtual machine is busy.]

Error Solution: Retry the backup/restore request.

 

Error Message: Delete snapshot failed for VM[Permission to perform this operation was denied.]

Error Solution: Check required user privileges.

 

VMWARE_VMOMI7

Error Message: Power off VM operation failed[The virtual machine is in invalid state]

Error Solution: If the current power state of virtual machine does not support to delete snapshot. Change power state of virtual machine. (power off the vm.)

 

Error Message: Power off VM operation failed[The virtual machine is busy, can't poweroff]

Error Solution: Retry request.

 

Error Message: Power off VM operation failed[Permission to perform this operation was denied.]

Error Solution: Check required user privileges.

 

VMWARE_VMOMI9

Error Message: VM reconfiguration operation failed[Duplicate name found in configuration spec.]

Error Solution:   To resolve name error:

  • Rename the duplicate entity.
  • See client log for more information about entity.

 

Error Message: VM reconfiguration operation failed[Invalid name found in configuration spec] OR

                                    VM reconfiguration operation failed[The virtual machine is in invalid state]

Error Solution:   To resolve the invalid name error:

  • Rename the duplicate entity and retry the operation.
  • See client log for more information about entity.

 

Error Message: VM reconfiguration operation failed[The virtual machine is busy]

Error Solution: Retry the backup/restore request.

 

Error Message: VM reconfiguration operation failed[Problem in VM configuration]

Error Solution: Check virtual machine configuration.

 

Error Message: VM reconfiguration operation failed[Permission to perform this operation was denied.]

Error Solution: Check required user privileges.

 

VMWARE_VMOMI10

Error Message: Unsupported disk [One or more disk is now independent vRDM or pRDM disk which were vRDM disk  during backup]

Error Description: This error can occur during restoring to original location.

Error Solution: To resolve the error:

  • Convert the independent vRDM /pRDM to original vRDM disk.
  • Try restoring to alternate location.

VMWARE_VMOMI11

Error Message: The problem with disk[Renaming the disk failed] OR

                                     The problem with disk. [Can not delete disk [<VMDK path>. Needs to be deleted manually.]OR

                                     The problem with disk. [Can not proceed as one or more vmdk files already exist.Error Description: This  error can occur during restoring to original                                             location.

Error Solution: To resolve the error:

  • Manually rename disk or move problematic vmdk and retry the operation.
  • Try restoring to alternate location.
  • Delete the mention vmdk disk using the steps listed here and then retry to restore to original location.
  • Contact Druva support.

VMWARE_VMOMI12

Error Message: Query for VMOMI object failed.[Temporary failure in querying VCenter/ESX host. Please retry  backup/restore request again.]VMOMI object failed.[Temporary failure in querying VCenter/ESX host. Please retry  backup/restore request again.]

Error Solution: Retry the operation.

VMWARE_VMOMI13

Error Message: Change area query failed.[CBT might not be enabled correctly. Please reset the CBT correctly and then  trigger backup request again.]

Error Description: This error can occur if the CBT of a virtual machine is not set correctly and the Backup Proxy version is less than 4.4.

Error Solution: To resolve the error:

  1. Login to the backup proxy.
  2. Reset the CBT of virtual machine using vmcontrol utility.

                                      For more information, see Use the VMcontrol utility to enable CBT.

If the error still persists, contact Druva support.

VMWARE_VMOMI65535

Error Message: Phoenix Internal Error

Error Solution: Contact Druva support.