Knowledge Base

• Cannot find customization specs during pool creation

Most likely a permissions problem. Check that your permissions are sufficient. See the documentation for more information about permissions.

Another cause could be that the customization spec has been renamed or deleted. Choosing a new spec for the desktop resolves this issue.

• Cannot find a cluster or datacenter during pool creation

Most likely a permissions problem. Check that your permissions are sufficient. See the documentation for more information about permissions.

• No templates are available in the template selection screen

Most likely a permissions problem. Check that your permissions are sufficient. See the documentation for more information about permissions.

• Provisioning failed with error message "VM not found"

The template is not accessible or the template name has been changed in VirtualCenter or the template was moved to a different folder in VirtualCenter.

• Provisioning failed with error message "Socket Error"

The likely cause is that VDM cannot connect to VirtualCenter. Verify that the VirtualCenter Web service is running and there are no network problems.

• Provisioning failed with error message "Out of disk Space"

This message indicates that the datastore used for the pool is out of disk space, or you do not have permission to access the selected datastore.

• Cloning failure

The pool manager disables provisioning when it encounters an error when cloning a virtual machine. This error message is displayed in the desktop's overview page.  

 

The following two log messages indicate that the VirtualCenter has been overloaded. Try reducing the provisioning and power operation limits for that VirtualCenter in VDM:

 

LDAP: error code 51 - 0000200E: SvcErr: DSID-02080499, problem 5001 (BUSY)

No disk space: Insufficient disk space on datastore 'm81 sdb (1)

The following log messages indicate a connection problem. Make sure you can connect to the VDM Connection server/VirtualCenter server.

WARN  <PendingOperation-/flat-dc/vm/bignp2/bignp2-5> [ServiceConnection] Problem while performing VC operation: '(0)null' [org.apache.axis.AxisFault] Message: (0)null

WARN  <PendingOperation-/flat-dc/vm/bignp2/bignp2-2> [ServiceConnection] Problem while performing VC operation: 'java.net.SocketException: Connection reset' [org.apache.axis.AxisFault] Message: ; nested exception is: java.net.SocketException: Connection reset Cause: java.net.SocketException: Connection reset

 

The following message means that VirtualCenter has been overloaded. Reduce the number of concurrent operations allowed for that VirtualCenter.

WARN  <PendingOperation-/flat-dc/vm/bignp2/bignp2-4> [ServiceConnection] Problem while performing VC operation: 'Permission to perform this operation was denied.' [com.vmware.vim.NoPermission]

•  Virtual machines stuck in Provisioning state

The connection server restarted during cloning operation or an operation failed. Delete the virtual machine and allow it to be cloned again.

• Virtual machines stuck in Customizing state

Virtual machines are stuck in the Customization state and the following error message is generated in the logs:

 

ERROR <PendingOperation-/flat-dc/vm/bignp2/bignp2-3> [PendingOperation] Pool cn=4a62ed61-686f-4e47-87f3-865f5ebc3c9d,ou=virtualcenter,ou=properties,dc=vdi,dc=vmware,dc=int::Unable to start VM /flat-dc/vm/bignp2/bignp2-3 - No disk space: Insufficient disk space on datastore

This message means that there is not enough disk space to start the virtual machine. A virtual machine must be started so that sysprep can work and customization can take place. In most cases, you can delete the virtual machine to recover from a stuck customization.  

• The virtual machine has been deleted or moved in ESX

If a virtual machine has been deleted or moved in ESX, the following error message is generated:

ERROR <PendingOperation-/flat-dc/vm/bignp2/bignp2-2> [PendingOperation] Pool cn=4a62ed61-686f-4e47-87f3-865f5ebc3c9d,ou=virtualcenter,ou=properties,dc=vdi,dc=vmware,dc=int::Unable to start VM /flat-dc/vm/bignp2/bignp2-2 - VM not found

Move the virtual machine back to the indicated VirtualCenter inventory folder or delete it from the VDM Administrator user interface.

• No virtual machines are being provisioned

When this happens, check the logs. You may see a log like the following:

INFO  <RePropagate cn=bignp2,ou=server groups,dc=vdi,dc=vmware,dc=int> [VirtualCenterDriver] cn=bignp2,ou=server groups,dc=vdi,dc=vmware,dc=int::Provisioning is disabled, can't clone 5 VMs

This is the result of the desktop having provisioning disabled because of an earlier error (which should be visible in the VDM Administrator user Interface) or because it has been purposely disabled.

Resolve any reported problems and reenable provisioning on the desktop.