We have 2 AppVolumes Managers and sometimes logon is very long (the 3 minutes timeout) and we see a box saying that appvolumes manager is unreachable.
So Appstacks are not connected even if the second server is reachable.
We have no network connectivity issue.
On the first server we see these errors in log files:
Re-using "Hypervisor <Multiple vCenters>" - 53 secs old - Not yet connected
On virtual desktop:
[svservice:P844:T4924] Successfully launched: svservice.exe message "Connection Error
The infrastructure is made of:
App Volumes 2.11 on Windows Server 2012 R2
Horizon 7.0.2 (virtual desktops are Windows Server 2012 R2)
vCenter 6.0 / ESXi 6.0
Have you any ideas?
Quick question. Are you not using any load balancer for the two App Volumes managers?
Sorry for the delay. The issue was resolved by setting IP address of App Volumes servers on virtual desktops insted of their names. I guess it's related to a name resolution issue.
It's ok to use IP address but please keep in mind that when you upgrade to App Volumes 2.12.0 or above, Certification validation will be enforced by default (higher security) and if you use cert validation, you will need to make sure you are using FQDN and not IP. It might be better to understand what's the cause of the name resolution, most likely a DNS issue.
Using SSL Certificates with App Volumes Manager (2148178) | VMware KB