Chapter 15 Troubleshooting View Components
Pool Provisioning Fails Due to Datastore Problems If a datastore is out of disk space, or you do not have permission to access the datastore, provisioning of a desktop pool can fail. Problem Provisioning of a desktop pool fails, and you see one of the following error messages in the event database. n
Provisioning error occurred for Machine Machine_Name: Cloning failed for Machine
n
Provisioning error occurred on Pool Desktop_ID because available free disk space is reserved for linked clones
n
Provisioning error occurred on Pool Desktop_ID because of a resource problem
Cause You do not have permission to access the selected datastore, or the datastore being used for the pool is out of disk space. 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
In View Administrator, reduce the maximum number of concurrent provisioning and power operations for vCenter.
n
Configure additional vCenter Servers. For more information about configuring vCenter, see the VMware View Installation document.
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.
VMware, Inc.
291