4.5

Table Of Contents
Solution
n
Verify that you have sufficient permissions to access the selected datastore.
n
Verify whether the disk on which the datastore is configured is full.
n
If the disk is full or the space is reserved, free up space on the disk, rebalance the available datastores, or
migrate the datastore to a larger disk.
Pool Provisioning Fails Due to vCenter Being Overloaded
If vCenter is overloaded with requests, provisioning of a desktop pool can fail.
Problem
Provisioning of a desktop pool fails, and you see the following error message in the event database.
Provisioning error occurred on Pool
Desktop_ID
because of a timeout while customizing
Cause
vCenter is overloaded with requests.
Solution
n
Reduce the provisioning and power operation limits for vCenter.
n
Reduce the number of concurrent operations that are allowed for vCenter.
n
Configure additional vCenter Servers.
For more information about configuring vCenter, see the VMware View Installation Guide.
Virtual Machines Are Stuck in the Provisioning State
After being cloned, virtual machines are stuck in the Provisioning state.
Problem
Virtual machines are stuck in the Provisioning state.
Cause
The most likely cause of this problem is that you restarted the View Connection Server instance during a cloning
operation.
Solution
u
Delete the virtual machines and clone them again.
Virtual Machines Are Stuck in the Customizing State
After being cloned, virtual machines are stuck in the Customizing state.
Problem
Virtual machines are stuck in the Customizing state.
Cause
The most likely cause of this problem is that there is not enough disk space to start the virtual machine. A
virtual machine must start before customization can take place.
Chapter 15 Troubleshooting View Components
VMware, Inc. 281