Vmware Connection Server Download 'LINK'
Tanja Mcinnis
I noticed that in the folder C:\Program Data\VMware\VDM\dumps there were some dumps from Tomcat service. At every restart ot the Connection server service a dump appeared with the size of about half a GB. I tried to open those dumps with Visual Studio, but I didn't find any useful information.
I have had this problem since the beginning, about a year ago. I'm on Horizon 7.13. This system was installed and setup by a consultant, first mistake. He was was given an impossible time line, second mistake. The problem is this. Almost all users are being directed to one Connection Server, I have two. It will not balance out the session between the two servers. I use a pair of UAG servers. Their connections are fairly balanced between them. They communicate with a load balancer in front of the Connection Servers. The load balancer has been checked twice and it's configuration verified by the vendor. I have talked to vmware support more than once and currently have an open case. Does anyone have any ideas why all sessions seem to gather on one Connection Server?
I created VMWare ssl web template from CA. Configured everything for Enroll. On the replica server - requested the certificate and completed the certificate process. Imported the certificate to Trusted Root Authorities folder as well. I did this after replica server was installed. I did delete self signed certificate that was created during replica server install. I deleted because did not needed as, I am using certificate from CA.
Just upgraded to the latest 7.0.1. Have done many upgrades without an issue. I have two connections server 01, 02. After the upgrade I was not able to login to my main one - 01. After being able to login via 02 I checked the status and the box is red and says "The service is not working properly" Tried restarting the services and the box numerous times and no luck.
It was just an upgrade from 7.0 to 7.0.1. I cannot get anything to load on 01. And all services are running properly and have been rebooted/restarted numerous times. I also checked the time between the servers and they seem fine.
Also check "\VMware\VMware View\Server\broker\webapps" directory for the following list of folder - admin, ROOT, portal. You can also try stopping the connection server services and then delete the admin and ROOT folders. After this start the connection broker service and check for viewadmin page.
I ran into this same issue with my upgrade last night from 7.0.0 to 7.0.1. I ended up calling into support to resolve the issue. The tech mentioned that sometime with two servers (connection and replica) that you have to update both servers to get the management portal to work. That didnt help my issue. I ended up having to uninstall the connection server, reboot, and then reinstall on both servers. After the reinstall all my pools and settings were present. Hope this helps
I ended up having a similar issue when upgrading from 6.2.2 to 7.0.1. The first connection server upgraded fine without issue. The second/replica install said it was successful but reported the same error you got in the Horizon Administrator. Tried the same thing of service restarts and reboots and those did not work either. Ran the installer again, once again said the install/upgrade was successful but still issues. After looking at it then, it was now actually missing the view connection server service and the application was not even shown as being installed. Ran the installer a third time, installed fine yet again services came up and the box finally registered with View/Horizon in a working state. Weird, but have not had any issues with it since.
should keep the configuration but take snapshots, backups, and write down settings of your environment before doing the upgrade like the documentation says. just in case. I didnt have an issue losing configuration on my upgrade. The first server went fine and picked up where it left off and the replica was the one giving me fits.
He resolved the problem by uninstalling the Horizon 7 Connection Server component from Programs & Features (leave the AD LDS Instance alone) before installing the 7.0.1 package. Not sure if it's necessary, but we rebooted after uninstalling and again after installing 7.0.1. You will be prompted to use the existing instance during install - click OK. This issue seems to be specifically related to connection servers that are paired with security servers. We're back online after following the procedure from Jacob's blog.
It's also a good idea if these servers are still around (recommended to do this first actually), to log into them and uninstall Horizon View (VMware Horizon 7 Connection server), the AD LDS Instance, Horizon HTML access and remove the AD LDS role in Server Manager.
Once you perform a full cleanup of the old or obsolete servers, replication should return to a healthy status. It might also be a good idea to restart the VMware Horizon View Connection Server service on each Connection server one by one.
I am unable to click on the HTML Access Client and get to my resources on the connection server through Chrome i get a "Failed to connect to Connection Server" But again this only happens in Chrome. Any suggestions?
We have the same issue and I was looking at the KB. This KB doesn't state it, but you have to create the locked.properties file. I read it in =en_US&cmd=displayKC&externalId=21447.... I was looking in my connection servers trying to find the locked.properties. I hope that this works.
I added the locked.properties file with the check=Origin=false line to all my connection servers. I can connect to each of the connection servers using the specific DNS name for each server through Chrome. What I can't do now is connect through a DNS name that our Security gave us to use. Using that DNS name will direct us to one of the connection servers that is available.
df19127ead