7.0

Cause
This can happen occasionally when a replica Connection Server is started while another Connection Server
is doing image operations.
Solution
n
If the error occurs during pool creation, enable provisioning if it is disabled. If it is enabled, disable and
then enable it.
n
If the error occurs during a push image operation, initiate another push image operation with the same
image.
Instant Clone Image Publish Failure
View administrator shows that an image publish failed.
Problem
After creating an instant-clone desktop pool or initiating a push image, you check the status of the operation
and View Administrator shows that the image publish failed.
Solution
n
Re-enable provisioning if it is disabled. If it is enabled, disable and then enable it. This causes View to
trigger a new Initial Publish operation.
n
If it is determined that the current image has some issues, initiate another push image operation with a
different image.
What to do next
If the image publish fails repeatedly, wait 30 minutes and try again.
Endless Error Recovery During Instant-Clone Provisioning
Error recovery falls into an endless loop during the provisioning of an instant-clone desktop pool
Problem
During provisioning, instant clones can go into an error state with the message "No network connection
between Agent and connection Server". The automatic error recovery mechanism deletes and recreates the
clones, which go into the same error state and the process repeats indefinitely.
Cause
Possible causes include a permanent network error or an incorrect path to the post-customization script.
Solution
u
Fix any error in the network or the path to the post-customization script.
Cannot Delete Orphaned Instant Clones
On rare occasions, during provisioning, an instant clone gets into an error state and you cannot delete the
desktop pool from View Administrator.
Problem
To delete the pool, View sends requests to vCenter Server to power off the clones. However, the requests fail
for clones that are orphaned. The result is that View cannot delete the pool.
Solution
1 From vCenter Server, unregister the orphaned clones.
Chapter 19 Troubleshooting Machines and Desktop Pools
VMware, Inc. 329