vRealize Broker Agent: This is NOT a valid View Connection Server

While performing an upgrade of both Horizon View and vRealize Operations Manager I ran into an issue where the Broker Agent for vRealize would not connect to the View Connection Server. A quick google search led me down the road for troubleshooting the broker agent connectivity, but everything seemed to point to issues with pairing the adapter. For me the adapter had no issue pairing with the vRealize Operations Manager server, it was failing on the second step with the connection server.

Some context:

Horizon View was recently upgraded from 6.2.0 to 6.2.4 and vRealize was upgraded from 6.1 to 6.5, along with the vRealize for Horizon adapter to 6.5.  The broker agent was installed on the first View Connection server, which was only used for internal LAN connections. The User name and password being used were tested against the View environment with no issues. All firewall ports were open on the vRealize Operations Manager as outlined here.

Ultimately this KB was the closest to the issue. In the environment we had used the locked.properties file to allow TLS 1.0 in order to support older thin clients. Without that file these clients would not work so building a new connection server seemed to be the best option.

Here you can see the locked.properties file that was current in use on the connection servers:



A new replica connection server was built. No custom configuration was done, but it was a member of the replica group already set up with the existing Horizon View Connection servers. By not creating the locked.properties file the broker agent was able to be installed on this new server. Be sure to uninstall the broker agent from the other view connection server first.

No locked.properties file on the new server:

The part I’m unsure on is whether the locked.properties file causes this issue just by existing or if it was the TLS 1.0 defined within it. As the KB referenced above mentions the locked.properties file could be defining the connection as localhost, but it wasn’t set to here.  The release notes do mention TLS 1.0 must be used for older agents, but that also did not apply in this environment.


If anyone knows whether simply having the locked.properties file causes this or it has something to do with TLS 1.0 I would love to hear about it.

If I get the chance to test this myself I will share the results.


Thanks for reading and I hope you find this helpful.

Leave a Reply

Your email address will not be published. Required fields are marked *