Hi All,
We keep getting the below error when adding a New Server to our VMWare view horizon client version 3.1.0.21879 :
Below is all the steps I have taken to resolve the issue:
— Added site to the proxy exception list GPO
— Added NO_PROXY environment variable
However I am still getting the issue the only way I can resolve is to open the proxy exception list remove all the site then re-add the sites.
Can you please advise how to resolve this issue I’ve attached the log file and also copied it below:
2014-12-16 13:44:56.731+00:00 INFO (0A58) [libcdk] Log for vmware-view.exe pid=4592 version=3.1.0-2085634
2014-12-16 13:44:56.731+00:00 INFO (0A58) [WinCDK] OpenLog : Log for VMware Horizon Client, version=3.1.0 build-2085634.
2014-12-16 13:44:56.731+00:00 ERROR (0A58) [WinCDK] RebrandingPref::LoadCertFile : Failed create new BIO from cert file: C:Program FilesVMwareVMware Horizon View Clientrcrebrandingvendor.crt.
2014-12-16 13:44:56.732+00:00 ERROR (0A58) [WinCDK] RebrandingPref::VerifyCert : Invalid parameter.
2014-12-16 13:44:56.732+00:00 ERROR (0A58) [WinCDK] RebrandingPref::CheckRebranding : Failed to verify cert.
2014-12-16 13:44:56.732+00:00 INFO (0A58) [WinCDK] utils::GetCurrentLangId : Language id ‘0x0409’ used by the OS.
2014-12-16 13:44:56.733+00:00 INFO (0A58) [libcdk] Using the WSAPoll() API Implementation for polling sockets.
2014-12-16 13:44:56.744+00:00 INFO (0A58) [libcdk] Using libcurl/7.32.0 OpenSSL/1.0.1h zlib/1.2.3 c-ares/1.9.1
2014-12-16 13:44:56.744+00:00 INFO (0A58) [libcdk] Set local language as en-us.
2014-12-16 13:44:56.835+00:00 INFO (0A58) [libcdk] Icon cache root dir will be:C:UsersropollAppDataRoamingVMwareVMware Horizon View ClientIcon Cache.
2014-12-16 13:44:56.885+00:00 INFO (0A58) [WinCDK] SmallWindow::OnInitDialog : [User] Enter SmallWindow.
2014-12-16 13:44:56.947+00:00 INFO (0A58) [WinCDK] SmallWindow::OnInitDialog : [User] Exit SmallWindow.
2014-12-16 13:44:56.960+00:00 INFO (0A58) [WinCDK] AppWindow::EnterWindowState : Valid transition from state ‘Uninitialized’ to state ‘Disconnected’.
2014-12-16 13:44:56.970+00:00 INFO (0A58) [WinCDK] NotificationAreaManager::ShowIcon : Create notify icon in the notification area succeed.
2014-12-16 13:44:56.970+00:00 INFO (0A58) [WinCDK] NotificationAreaManager::ShowIcon : Set version for the notify icon succeed.
2014-12-16 13:44:56.974+00:00 INFO (0A58) [WinCDK] ImageItem::OnPaint : Current system’s BITSPIXEL: 32.
2014-12-16 13:44:58.156+00:00 INFO (0A58) [WinCDK] AppWindow::OnAddServer : [User] Enter AddServer.
2014-12-16 13:44:58.160+00:00 INFO (0A58) [WinCDK] AddServerDlg::OnInitDialog : [User] Enter AddServerDialog.
2014-12-16 13:44:58.165+00:00 INFO (0A58) [WinCDK] AddServerDlg::OnInitDialog : [User] Exit AddServerDialog.
2014-12-16 13:46:14.334+00:00 INFO (0A58) [WinCDK] ImageItem::OnPaint : Current system’s BITSPIXEL: 32.
2014-12-16 13:46:18.930+00:00 INFO (0A58) [WinCDK] AddServerDlg::OnOk : [User] Enter Ok.
2014-12-16 13:46:18.934+00:00 INFO (0A58) [WinCDK] AddServerDlg::OnOk : [User] Exit Ok.
2014-12-16 13:46:18.935+00:00 INFO (0A58) [WinCDK] Services::LogOffServer : [User] Enter Services::LogOffServer.
2014-12-16 13:46:18.935+00:00 INFO (0A58) [WinCDK] Services::LogOffServer : [User] Exit Services::LogOffServer.
2014-12-16 13:46:18.936+00:00 INFO (0A58) [WinCDK] AppWindow::EnterWindowState : Valid transition from state ‘Disconnected’ to state ‘Connecting’.
2014-12-16 13:46:18.941+00:00 INFO (0A58) [WinCDK] AppWindow::OnAddServer : [User] Exit AddServer.
2014-12-16 13:46:18.941+00:00 INFO (0A58) [libcdk] TaskCombiner: CdkGetLaunchItemsTask(TODO) added, group task num:1, total task num:1.
2014-12-16 13:46:18.942+00:00 INFO (0A58) [libcdk] TaskCombiner: CdkGetUserGlobalPreferencesTask(TODO) added, group task num:2, total task num:2.
2014-12-16 13:46:18.973+00:00 DEBUG (0A58) [(null)] CdkProxy_GetProxyForUrl: Got the proxy and return to main message loop.
2014-12-16 13:46:18.973+00:00 INFO (0A58) [libcdk] TaskCombiner: CdkGetTunnelConnectionTask(TODO) added, group task num:3, total task num:3.
2014-12-16 13:46:18.973+00:00 INFO (0A58) [libcdk] TaskCombiner: Group Tasks(3):CdkGetLaunchItemsTask(TODO),CdkGetUserGlobalPreferencesTask(TODO),CdkGetTunnelConnectionTask(TODO),
2014-12-16 13:46:18.973+00:00 INFO (0A58) [libcdk] TaskCombiner: CdkGetConfigurationTask(TODO) added, group task num:1, total task num:4.
2014-12-16 13:46:18.973+00:00 INFO (0A58) [libcdk] TaskCombiner: CdkSetLocaleTask(TODO) added, group task num:2, total task num:5.
2014-12-16 13:46:18.973+00:00 INFO (0A58) [libcdk] TaskCombiner: Group Tasks(2):CdkGetConfigurationTask(TODO),CdkSetLocaleTask(TODO),
2014-12-16 13:46:18.973+00:00 INFO (0A58) [libcdk] TaskCombiner: CreateRequest for CdkSetLocaleTask(REDY).
2014-12-16 13:46:18.977+00:00 INFO (0A58) [libcdk] Send request successful: 026F6650
2014-12-16 13:46:19.021+00:00 INFO (0A58) [libcdk] Got a response to request 1.
2014-12-16 13:46:19.021+00:00 INFO (0A58) [libcdk] TaskCombiner: CdkGetLaunchItemsTask(FAIL) removed, group task num:2, total task num:4.
2014-12-16 13:46:19.021+00:00 INFO (0A58) [libcdk] TaskCombiner: CdkGetUserGlobalPreferencesTask(FAIL) removed, group task num:1, total task num:3.
2014-12-16 13:46:19.022+00:00 INFO (0A58) [libcdk] TaskCombiner: CdkGetTunnelConnectionTask(FAIL) removed, group task num:0, total task num:2.
2014-12-16 13:46:19.022+00:00 INFO (0A58) [libcdk] TaskCombiner: CdkGetConfigurationTask(FAIL) removed, group task num:1, total task num:1.
2014-12-16 13:46:19.022+00:00 INFO (0A58) [libcdk] TaskCombiner: CdkSetLocaleTask(FAIL) removed, group task num:0, total task num:0.
2014-12-16 13:46:19.022+00:00 INFO (0A58) [WinCDK] Services::HandleErrorCallback : Error(Taskname:CdkSetLocaleTask, domain:1, code:48) Callback: Entry.
2014-12-16 13:46:25.223+00:00 INFO (0A58) [WinCDK] AppWindow::EnterWindowState : Valid transition from state ‘Connecting’ to state ‘Disconnected’.
2014-12-16 13:46:25.226+00:00 INFO (0A58) [WinCDK] ImageItem::OnPaint : Current system’s BITSPIXEL: 32.
2014-12-16 13:46:25.228+00:00 INFO (0A58) [WinCDK] Services::HandleErrorCallback : Error(Taskname:CdkSetLocaleTask, domain:1, code:48) Callback: Exit.
Many organizations are making use of VMware Horizon as the solution to enable a successful, effective, and efficient remote work environment. VMware Horizon is able to connect remote workers to VDI environments and even physical machines. With that being said, issues may arise from time to time where your end-users may not be able to connect to the target machine in their desktop pool, whether virtual or physical. Let’s take a look at VMware Horizon Client Error couldn’t connect to server and see some common troubleshooting steps you may need to take to resolve your connectivity issue.
Know your architecture
In order to troubleshoot Horizon effectively, you need to know your architecture in the Horizon environment. How does traffic flow from the outside to your Horizon desktop? Are UAGs in play, Load Balancers, VIPs, multiple Horizon connection servers? Also, what is the state of the agent on the endpoint machine.
Also, just basic troubleshooting methodologies here, but was the target machine working and then stopped? What has changed, anything? Note the architecture of the below diagrams. In the first image, we have a Horizon Client connecting directly to Horizon Connection Servers.
Below, the Horizon Client first connects to the Unified Access Gateway servers which then connect to Horizon Connection Servers and the Horizon Agent Virtual Desktop. One tip here, if you have UAGs in play, you can still test a connection from the Horizon Client directly to the Horizon Connection Server. This connection should be successful. If you can successfully launch a session when directly connected to your Horizon Connection Server from the Horizon Client, you know the issue is somewhere above the Horizon Connection Server – the UAGs, firewall rules, load balancer, VIPs, etc.
Using that trick can help to shortcut troubleshooting to narrow in on where the connectivity issue exists. If you can’t connect to one Horizon Connection server, try the other Connection Server if you have multiples. If you can connect using one and not the other, this narrows in on a potential issue with a particular Connection Server.
There are a few obvious things to check when users have VMware Horizon Client error couldn’t connect to server. If you have already ruled out the obvious reasons for connectivity issues, such as changing a firewall rule and other clients are connected just fine, you most likely do not have a global issue with the environment. Next, look at the specific Desktop pool > Machines. Note what the status is for the Desktop machine configured for the desktop pool.
If the agent is unreachable, the client will never be able to connect. At that point, you need to figure out why the Horizon Connection server cannot “see” the agent. Is the agent service running? Is the machine down? If the machine exists on a separate network, do you have network level connectivity to the machine in question? Is NAT in play?
VMware Horizon Agent physical machines
With physical machines, I have had to implement a registry key in some environments for connecting successfully to remote physical workstations. ***Note***. This has been tested with Horizon 7 only and may not be needed with Horizon 8. However, it is worth trying if you are having weird issues not being able to connect to physical workstations with the Horizon agent installed.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINESOFTWAREVMware, Inc.VMware VDMPluginswsnmdesktopParams]
"UsePPNotificationsForSessions"="true"
[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerWinStationsVMware-RDS]
"fEnableWinStation"=dword:00000000Physical machines also do not like to have a user logged into the console and then a connection attempt from Horizon. It will either error or give a message that there are no sessions available.
VMware Horizon Agent Endpoints with NAT translation
The VMware Horizon Agent reports the actual IP address back to the Horizon Connection server that is local to the machine itself. However, what if your connection server does not have a route to that internal network represented by the local IP address? It can cause issues as the Horizon Connection Server attempts to make connection with the private IP reported by the Horizon Agent.
The Horizon Agent reports the discovered IP address of the machine on which it is running to the Connection Server instance. In secure configurations where the Connection Server instance cannot trust the value that Horizon Agent reports, you can override the value provided by Horizon Agent and specify the IP address that the managed machine should be using. If the address of a machine that Horizon Agent reports does not match the defined address, you cannot use Horizon Client to access the machine.
In this case, the vdmadmin command can be a lifesaver. You can use the vdmadmin command with the -A option to override the IP address reported by Horizon Agent. Note the examples given by VMware:
Override the IP address for the machine machine2 in the desktop pool dtpool2.
vdmadmin -A -override -i 10.20.54.165 -d dtpool2 -m machine2
Display the IP addresses that are defined for the machine machine2 in the desktop pool dtpool2.
vdmadmin -A -override -list -d dtpool2 -m machine2
Remove the IP addresses that is defined for the machine machine2 in the desktop pool dtpool2.
vdmadmin -A -override -r -d dtpool2 -m machine2
Remove the IP addresses that are defined for the desktops in the desktop pool dtpool3.
vdmadmin -A -override -r -d dtpool3
VMware Horizon Agent machine with multiple IP addresses
What about a VMware Horizon Agent machine running multiple IP addresses? The Horizon Agent can report the wrong IP to the Horizon Connection Server. There is a special registry key for this case. Note the VMware KB here:
- Configure a Virtual Machine with Multiple NICs for Horizon Agent (vmware.com)
On the virtual machine on which Horizon Agent is installed, open a command prompt, type regedit.exe and create a registry entry to configure the subnet.For example, in an IPv4 network:
HKLMSoftwareVMware, Inc.VMware VDMIpPrefix = n.n.n.n/m
(REG_SZ)In this example, n.n.n.n is the TCP/IP subnet and m is the number of bits in the subnet mask.Wrapping Up
If you get VMware Horizon Client Error Couldn’t Connect to Server or another similar error, methodical troubleshooting can help to narrow in on where the issue exists. VMware Horizon relies on many different components to the infrastructure that need to be verified. However, there are a few configuration areas as mentioned that can lead to difficulty connecting to the VMware Horizon Agent virtual or physical machine. Hopefully, these few notes can help any struggling with connectivity issues.
Last night I updated my VMware VDI envionrment to VMware Horizon 7.4.0. For the most part the upgrade went smooth, however I discovered an issue (probably unrelated to the upgrade itself, and more so just previously overlooked). When connecting with Google Chrome to VMware Horizon HTML Access via the UAG (Unified Access Gateway), an error pops up after pressing the button saying “Failed to connected to the connection server”.
The Problem:
This error pops up ONLY when using Chrome, and ONLY when connecting through the UAG. If you use a different browser (Firefox, IE), this issue will not occur. If you connect using Chrome to the connection server itself, this issue will not occur. It took me hours to find out what was causing this as virtually nothing popped up when searching for a solution.
Finally I stumbled across a VMware document that mentions on View Connection Server instances and security servers that reside behind a gateway (such as a UAG, or Access Point), the instance must be aware of the address in which browsers will connect to the gateway for HTML access.
The VMware document is here: https://docs.vmware.com/en/VMware-Horizon-7/7.0/com.vmware.horizon-view.installation.doc/GUID-FE26A9DE-E344-42EC-A1EE-E1389299B793.html
To resolve this:
On the view connection server, create a file called “locked.properties” in “install_directoryVMwareVMware ViewServersslgatewayconf”.
If you have a single UAG/Access Point, populate this file with:
portalHost=view-gateway.example.com
If you have multiple UAG/Access Points, populate the file with:
portalHost.1=view-gateway-1.example.com
portalHost.2=view-gateway-2.example.com
Restart the server
The issue should now be resolved!
On a side note, I also deleted my VMware Unified Access Gateways VMs and deployed the updated version that ship with Horizon 7.4.0. This means I deployed VMware Unified Access Gateway 3.2.0. There was an issue importing the configuration from the export backup I took from the previous version, so I had to configure from scratch (installing certificates, configuring URLs, etc…), be aware of this issue importing configuration.
I noticed today that myself and our end users are getting a generic SSL error message:
Error: An SSL error has occurred
This is showing up in the Horizon client, and on our thin clients. We’re on Horizon 6.0.1 and have 1 load balancer, 2 security servers, and 4 connection servers. After this message pops up you can just click on okay, and then reconnect and it will work just fine.
I’m not completely sure where to start on troubleshooting this.
It happens internally and externally. We have a load balancer that everybody connects to that distributed the session to 4 different connection servers. If I manually connect to the servers I do not receive the SSL error, but when I connect to our main generic URL I get the error. The sys admins are tied up all day so I’m trying to troubleshoot this on my own as much as I can.
The only thing I’ve done sofar is browse out to our generic vmview address view a web browser, and check the certificate. The certificate is still active/valid.
Are there any log files on the security servers or connection servers that I can look in to to narrow this down?
I have been seeing this a lot when deploying the Horizon at clients lately. Failed to connect to the Connection Server. This is just straight hitting the VMware broker directly. No UAG or any other items in place. WHAT GIVES?
Thankfully, this is a pretty simple issue to fix. It’s a well documented fix but does have a variety of symptoms. I end up searching for it all the time so this is my chance to document the one I run into the most.
The scenario I run into the most is when there is a load balancer involved or weird domain networking. Different URLs and other HOST file chicanery.
I always end up on this locked.properties KB article.
The easy fix for all this is to create a locked.properties file with the single line checkOrigin=false place on each broker under:
If you are running Horizon 8 version 2106 or later, check out the post below
VMware Horizon – Failed to connect to the Connection Server – v2106 and Above!
In Timeline
By Carlo Costanzo
Here’s an OLD error message with an entirely new fix! “Failed to connect to the Connection Server” I have been running into this issue for the past few years and always go to the locked.properties file on the VMware Horizon connection server for the fix. The fix involved adding in a checkOrigin=false line into the […]
Read more
Restart all Horizon services and you should be good to go.
Happy Troubleshooting!
– Carlo
Hello,
We currently have a pool of 4 virtual machines, each of them are setup identically with Windows 10 1709. These 4 machines are child images which are based off of a master image. Within the last week or so, 1 of the 4 machines can no longer be connected to. Whenever a connection attempt is made from VMWare Horizon Client, the screen will go black and eventually close with the error message: «The remote desktop connection has ended». We have tried recomposing off the master image, disconnecting it from the PersistentData drive and connecting to it through Horizon using other machines. At this point, we are stumped on what the root cause is and what changed. The other 3 virtual machines can be connected to and used without issues. An interesting item of note is the problem virtual machine is completely unpingable from any machine that we’ve tested from so far. Any suggestions?
Note: The problem virtual machine cannot be connected to through Microsoft Remote Desktop Connection or VMWare Horizon.
Having the following error trying to convert a live CentOS/RHEL Linux system with VMware Converter?
FAILED: A general system error occurred:
Network error. Host x.x.x.x key can’t be retrieved. (return code 2)
In my case, this happened while converting a RHEL 5.11 server with VMware Converter 6.1.1.
If you went through the following :
– SSH configuration is allowing root to access the system remotely from port 22
– IPtables allow connection on port 22
– You are running Converter version 5.5.1 or greater (there is a known issue with older version that aren’t supporting DSA keys)
Then it might be caused by the “hosts.allow” parameter. Edit the following file :
And make sure you have the following entered (usually this file is blank on vanilla systems) :
Alternatively, you can restrict the subnet from where the connection come from by entering the following (this example will allow subnet “10.10.5.0/24) :
Restart the network service :