Can you share more about your environment? ESX, Horizon View, Windows OS and Horizon Agent version?
Can you do a full restart of the connection servers, seems like there could be a replication problem. Look at
if you haven't seen it before. Seems like a replication problem without looking at any logs, vcenter is deleting the VM quicker the replication is happening, which places them in the missing status. I seem to need to do this every 6 months.
Esxi 6.0 U3
Vcenter Server 6.5
New upgrade to View 7.4 Agent 7.4
Win7, Win 10
According to the admin console there are no replication issues between the servers but i will take at look at the article. Thanks
1 person found this helpful
We were seeing a similar issue provisioning linked clone that would report "(missing)" before the provisioning completed. Following Restart order of the View environment to clear ADLDS (ADAM) synchronization in Horizon View (2068381) fixed it for us.
Update: This turned out to be a known bug in 7.4.0. File a SR to get the hot patch that fixes it (7.4.0 build-8215536).
See my later posts in this thread.
We have the same error on Instant Clones pool [Error (missing)] and also we are experiencing an error in Linked Clones provisioning where deployment stops with:
Error during provisioning: Unable to find folder /VDI/vm/CLIENT/xxxxxxx even if the folder on vCenter has been correctly created.
It seems an ADAM sync problem.
We disbled all VM backups with snapshot (Avamar) to avoid unsynced ADAM DB on the Connection Servers due to VM quiescence and also restarted the whole environment as suggested with no luck.
Horizon 7.4 with Agent 7.4
This is the exact issue I saw before. Did you include vcenter in your restart. From my recollection the logons are session based to vcenter and the new session wasn't replicated in the database, which is showing outdated information. You want to make sure you restart vcenter while all connection servers are off, then start each one at a time verifying they start. The first one takes the longest.
Hi sjesse, yes we restarted also vCenter following the KB you suggested.
The KB does not mention Horizon 6.2 (that we have in Production with no issues) nor 7.4 that is our new environment with issues.
Restarting all environment did not help because after a first correct provisioning, problem occurred again in few hours.
Furthermore we reinstalled all Horizon environment last friday (apart vCenter) from scratch. Then we managed to create correctly 5 pools until today when error occured again without any change whatsoever to the infrastructure.
I am getting the same behavior on instant and linked clones.
I’ve opened a SR because I cannot find a solution.
Do you get a feedback from support? Is that a known issue?
Super6VCA I'm pretty sure you are experiencing the same known bug in 7.4.0 that we are. If you file an SR there is a sandbox build available if you date. The bug is targeted to be resolved in 7.5.0. You can workaround the issue by disabling provisioning, shutting down all of your connection servers, power them on one at a time and then enable provisioning. Essentially the steps in Restart order of the View environment to clear ADLDS (ADAM) synchronization in Horizon View (2068381) but you don't need to shutdown Composer or restart vCenter. We are having to follow this workaround daily in one of our pods. In the other pod we've never seen this issue.
I am also on 7.4 with our complete platform.
I´ve already opened a SR@VMware...
Tricky for me is that we are using Linked and Instant Clones in our environment.
I´ve heard that the next release (7.5) will discontinue Lined Clones...
For now I will wait for the feedback from support.
Did you get this solved by support or?
I seem to have the same issue with instant clones in a POC setup.
Yes, I got a feedback:
There is a hotfix available, but it will be final implemented into the next release of Horizon View (4.5).
Horizon 4.5 will be released next month.
For now we have opened a PR@VMware and we are hoping that we get the fix for our production environment.
A PR takes some approval time and maybe the next release will come before we get the approval.
I´ll keep you updated.