VMWARE_VMOMI1

This error can occur in multiple scenarios.

Error Message	Resolution
Snapshot of VM failed [Problem in VM configuration.]	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 Druva virtual machine backup policy. OR Unselect the Quiesce guest file system option if quiescing is disabled on the Druva virtual machine backup policy. For Windows virtual machine, check if the Virtual disk service is on. For more information see, QUIESCING-ERROR” in vCenter Server. Check if there is any third party VSS provider registered on the virtual machine. For more information see, Cannot create a quiesced snapshot of a virtual machine. Related KB article See, VMware KB 1007696
Snapshot of VM failed[Another snapshot of VM might be in the progress.]	Wait for the old snapshot to complete and trigger another backup/restore request.
Snapshot of VM failed [The number of levels in the Snapshot tree exceeds the supported maximum limit.]	Consolidate or delete the old snapshot and retry the operation.
Snapshot of VM failed[The VM is in invalid state to take snapshot.]	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.
Snapshot of VM failed[Incompatible device are present on VM.]	A backup fails if the Small Computer System Interface (SCSI) Controller is in sharing mode. This is because VMware does not support snapshot of virtual machines that are in bus-sharing mode. Ensure that the SCSI mode is not set to bus-sharing. For more information, see the troubleshooting section.
Snapshot of VM failed[Permission to perform this operation was denied.]	Check for the privileges.
Snapshot of VM failed[An error occurred while quiescing the virtual machine. Please retry the backup/restore again.]	Install or update the VMware tools on the virtual machine and retry the operation. Related KB article See, VMware Backups fails with error VMWARE VMOMI1
Snapshotof VM failed [Current license or ESXi version prohibits execution of the requested operation.]	Check the vCenter, ESXi version and the license details. You must use the version of the vCenter and ESXi that are supported by Druva. For more information, see Support matrix. Related KB article See, How to verify whether the ESX/vSphere host is licensed for vStorage APIs

VMWARE_VMOMI2

Error Message	Resolution
Reverting of snapshot Failed for VM[Another snapshot of VM might be in the progress]	Wait for the old snapshot to complete and trigger another backup/restore request.
Reverting of snapshot Failed for VM[The VM is in an invalid state.]	If the virtual machine is invalid or orphaned then the snapshot of such a virtual machine is not supported.
Reverting of snapshot Failed for VM[Problem in VM configuration]	Check the virtual machine configuration and see client log for more information about which virtual machine configuration entity caused the issue.
Reverting of snapshot Failed for VM[Permission to perform this operation was denied.]	Check required user privileges.

VMWARE_VMOMI3

Error Message	Resolution
Problem with Datastore.[Problem with datastore <datastore_name>]	To resolve problems with data store: Check if the data store is writable or not. Check if the data store is accessible from ESX host at the place of restore.
Problem with Datastore[Move disk operation failed.]	To resolve problems with the move disk operation: Check if the datastore is writable. Check if datastore is accessible from ESX host, where you are trying to restore. Rename or manually move the problematic disk. In case of restore to an alternate location, you can select another data store
Problem with Datastore[Unable to locate the datastore [<datastore_name>]]	To resolve problems with locating data store: Check whether the mentioned data store is accessible from vCenter or ESX. In case of restore to an alternate location, select another data store.
Cannot allocate memory (0xbad0014, Out of memory). 📝 Note This error message is displayed in the vmware.log* file.*	Migrate the virtual machine to another ESX. For more information see, Backing up the virtual machine fails when CBT is enabled[External link to VMware knowledge base].

VMWARE_VMOMI4

Error Message	Error Description	Resolution
No disk space available [No disk space available to create new VM].	This error can occur if there is inadequate disk space on the data store to restore the selected virtual machine.	To resolve the error: Manually free some disk space in the data store and retry the operation. OR Select some other data store with adequate disk space.
Restore process required <amount of> bytes free disk space, <amount of> bytes free disk space available on datastore <datastore name>.

VMWARE_VMOMI5

Error Message	Error Description	Resolution
Create new operation failed[Host capability max supported VMs is exceeded]	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.	To resolve the error: Delete at least one virtual machine and retry the restore request. OR Try to restore the virtual machine to other ESX hosts.
Create new VM operation failed. [The virtual machine version is not compatible with the version of the host <IP address of the host>]	This error can occur if a virtual machine is backed up from a host is incompatible with the host it is restored on. For example, if a virtual machine is backed up from vCenter 6.7, the restore fails if it is restored to vCenter 6.5.	To resolve the error, restore the virtual machine to a compatible host. For more information, see ESXi/ESX hosts and compatible virtual machine hardware versions list.[External link to VMware Knowledge Base.]

VMWARE_VMOMI6

Error Message	Resolution
Delete snapshot failed for VM[The VM is in invalid state]	If the current power state of the virtual machine does not support to delete the snapshot. Change the power state of the virtual machine. (power off the Virtual machine.) For more information on the invalid state of the virtual machine, see Virtual machines appears as invalid or orphaned in the vCenter server[External link to VMware knowledge base].
Delete snapshot failed for VM[The virtual machine is busy.]	Retry the backup/restore request.
Delete snapshot failed for VM[Permission to perform this operation was denied.]	To resolve this error, either: Provide the required permissions to the user whose credentials you have entered at the time of configuring the backup proxy. For more details on the permissions required for backup or restore virtual machines, see Required User Permissions. Reconfigure the backup proxy and provide credentials of the vCenter/ESXi user who has the required permissions. To reconfigure a backup proxy, see: Reconfigure backup proxy settings for vCenter server

VMWARE_VMOMI7

📝 Note

You encounter this error when you try to restore a virtual machine to the original location.

Error Message	Resolution
Power off VM operation failed[The virtual machine is in invalid state]	If the current power state of the virtual machine does not support to delete the snapshot. Change the power state of the virtual machine. (power off the virtual machine.) For more information on the invalid state of the virtual machine, see Virtual machines appears as invalid or orphaned in the vCenter server [External link to VMware knowledge base].
Power off VM operation failed[The virtual machine is busy, can't poweroff]	Retry request.
Power off VM operation failed[Permission to perform this operation was denied.]	To resolve this error, either: Provide the required permissions to the user whose credentials you have entered at the time of configuring the backup proxy. For more details on the permissions required for backup or restore virtual machines, see Required User Permissions. Reconfigure the backup proxy and provide credentials of the vCenter/ESXi user who has the required permissions. To reconfigure a backup proxy, see: Reconfigure backup proxy settings for vCenter server

VMWARE_VMOMI8

Error Message:Power on VM operation failed. [Problem in VM configuration.]

Error Description:This error can occur if a virtual machine cannot be powered on.

Error Solution:To resolve the error, check the virtual machine configuration.

VMWARE_VMOMI9

📝 Note

You encounter this error when you try to restore a virtual machine to the original location.

Error Message	Resolution
VM reconfiguration operation failed[Duplicate name found in configuration spec.]	To resolve the name error: Rename the duplicate entity. See client log for more information about the entity.
VM reconfiguration operation failed[Invalid name found in configuration spec]	To resolve the invalid name error: Rename the duplicate entity and retry the operation. See client log for more information about the entity.
VM reconfiguration operation failed[The virtual machine is in invalid state]
VM reconfiguration operation failed[The virtual machine is busy]	Retry the backup/restore request.
VM reconfiguration operation failed[Problem in VM configuration]	Check virtual machine configuration.
VM reconfiguration operation failed[Permission to perform this operation was denied.]	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 a restore to the original location.

Error Solution:To resolve the error:

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

VMWARE_VMOMI11

📝 Note

This error can occur during restore to the original location.

Error Message:

The problem with disk[Renaming the disk failed]
The problem with the disk. [Can not delete disk [<VMDK path>. Needs to be deleted manually.]
The problem with the disk. [Can not proceed as one or more vmdk files already exist.

Error Solution:To resolve the error:

Manually rename disk or move problematic vmdk and retry the operation.
Try restoring to an alternate location.
Delete the mention vmdk disk using the steps listed here and then retry to restore to the original location.
Contact 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 Description: This issue occurs when VMOMI is unable to fetch the Managed Object.

Error Solution: This can be a transient issue on VMware and may get resolved if you 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.

Resolution:To resolve the error:

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

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

If the error persists, contact Support.

VMWARE_VMOMI21

Error Message:Internal error [Snapshot Task is timed out]

Error Description:This error can occur during a backup when a VM snapshot takes longer than one hour to complete.

Resolution:Some of the reasons why a VM snapshot takes a longer time to complete are:

VM tools are not installed.
VM tools support VSS as the snapshot provider for Windows VMs, but the updated version of VMware tools needs to be installed with VSS support and configured.
Disk I/O issues of the VM.

You must retry the backup once you have resolved the above issues.

VMWARE_VMOMI65535

Error Message:Phoenix Internal Error

Resolution: Contact Support.

Related KBs:

Encrypted VM backup shows the Invalid configuration for device error on VMWare backup proxy

Restore VMware virtual machine data

Troubleshoot VMware issues

VMware errors

Monitoring VMware jobs