Still problems during provisioning a new automated pool.
I'm getting following error: Error during provisioning : unable to find folder /Datacenter/vm/testICT
During provisioning, the only thing he did was creating this folder, so the folder actually exists, you can see it in the printscreens. So i don't know why he stops provisioning the automated (linked clones) desktop pool.
Has someone got this strange error before? Or someone with a solution?
here you can see some printscreens, chronological:
Nobody who recognizes this problem?
I recognize that problem, I'm going through the exact same thing right now. Did you ever get it resolved?
It was allworking fine until windows updates and a reboot happened last week. Now a pool that was successfully creating VMs in it has the VMs listed as missing ever after it creates them. And any new pool does exactly what you are experiencing; creates the folder then can't find it.
I've checked firewalls, ports, rights... nothing is wrong.
I didn't find a solution. But we changed now from sql to oracle and that problem was solved. Now we're running on Oracle for composer.
But we never found an specefic solution.
When you changed from SQL to Oracle did you rebuild any of the VMware servers? Like View, vCenter...
Yes, we had te reinstall the view composer on the vCenter and also you have to remove the vcenter and re-add the vcenter in your view administrator (web based connection server). This is to reinitialize the connection with the new composer settingson the vcenter.
Got this fixed today.
The solution: Restart the View Server services. This knocked active View clients offline, but luckily we had only one person using it at the time.
This didn't correct my issue. I restarted the view connection server and adam instances on both of my brokers but now it doesn't seem to even try to provision desktops as there are no error or success messages in the events database.
Has anyone determined what causes this error since October?
I found this VMware KB http://kb.vmware.com/kb/1038077
I rebooted my View Manager as well as my vCenter server and everything started working fine for me.
This is a complete unacceptable solution