Hi Everyone,
I got one strange error on end-user machine saying that can not connect app vol manager, but I can ping manager from end-user VDI machine
Please find the below pic for more information.
Hi Vkmr,
Are you sure the specific agent is looking at the correct address and port for the manager?
To verify on the machine with the agent installed, please check:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\svservice\Parameters
In addition, check if the certificate is trusted:
Using SSL Certificates with App Volumes Manager (2148178) | VMware KB
To disable: VMware Documentation Library
To replace: Replacing the Self-Signed Certificate in VMware App Volumes 2.12
Regards,
If you haven't fixed this yet, try looking at your dhcp logs and see if the virtual had problems getting an ip address. I've seen a case where virtuals wouldn't get an ip address for a long time, and then they would. I think app volumes service times out after awhile(I think 3 minutes) and it won't try and reconnect, even though it finally got a correct ip address. I our case a vlan wasn't tagged on one of the two switches we where using for this environment. This made one virtuals on one blade get ip addresses, and not on another.
Is it port 80?
I can see "app-volume-manager-name:80"
It is randomly happening with random users
When you install the manager you can select if it accept incoming unsafe connections on port 80, by default this options is disabled so it WON'T accept connections on port 80.
If you did not select this option and you installed the manager with port 80 and not port 443 you could end up with an agent that cannot connect to the manager. Either reinstall the agent and select port 443 (HTTPS) or reinstall the manager and make sure to select the option to also allow unsafe connections.
To be honest I would select option 1. reinstall the agent and make sure to connect using https (port 443).
Even with correct setting of agent connection and or SSL verification I have experience this behavior randomly , and when we open call with VMware the couldn’t have direct answer and at the end they said upgrade to latest version
I had this issue when my agents and manager were not on the same version. The agent and manager logs should give you more details as to what the issue it.
I am with you techguy129, My agent and manager are running accordingly and unfortunately it is happening randomly, I will keep an eye on log's if I see it next time
Thank you,
Vkmr.
This occurred at my VMware Horizon View environment after transferrring DHCP service from one DC to a new DC.
After reversing my actions, all clear again.
cheers