Error During Provisioning

[KGoch]

I just setup an Automated Dekstop Pool and had provisioning Enabled. When I finished the setup it started provisioning but seems to have errored out. On the Summary page this error is present:

"Error during provisioning4/13/09 12:16:31 PM EDT: ; nested exception is: java.net.SocketTimeoutException: Read timed out "

Also there is a Clone Virtual Machine task that has been stuck at 94% for a while now too.

Im not sure what caused this. So Im guessing I need to start over from scratch or is there a way to stop and restart the provisioning?

Thanks!

[Linjo]

Hi.

Did the vCenter-task timeout or finish?

Actually its at 94% where the actual first copy is made in your first datastore, so this could take a little while depending on how fast your storage is and how big the golden master VM is. The subsequent linked clones should be much faster.

You could check on the storageside if the copy is still increasing in size or stopped at some point.

If it stopped, check the desktop composer logs.

BR

Linjo

[stanyarbroughjr]

Folks having this provisioning error in View 5.0 :-

Not sure why this is happening but the customization script kicks off before the replica is built during an initial or a recompose for a pool.

The best way to get past this is to select the failed desktops and press the remove button.  If the composer generated an error and the pool is set to stop on error, make sure that provisioning is re-enabled.

Once the desktops are deleted, then Composer will kick off to create new desktops to fullfil the pool desktop count.

(ie: if the pool count is 5 and 3 desktops errored, remove the 3 and 3 new ones will be created!)

****  Also noticed that the Manual service "VMware Universal File Access" was running on the vCenter Server with Composer.  Restarting Composer and stopping this service seemed to also fix the composer timing  *****

Stan

[nonsparker]

Did you ever get resolution to this issue? I am having to restart the Composer service as well and I was wondering if there was a more permanant fix.