Cant view admin console after Horizon 7.4 upgrade

[John_Getzke]

Hello,

We are attempting to upgrade a few test servers from Horizon View 7.0.3 to 7.4.0 by using the upgrade process without a full reinstallation.  The upgrade itself appears to be successful yet access to the web console/admin console does not appear to work.  Various browsers produce various errors all suggesting the website on the upgraded server is not available.

The best clue we have detected so far has to do with certs.  We have tried multiple cert configurations but are not able to access the admin console including:

- Generate new self-signed cert, then upgrade

- Remove self-signed cert, then upgrade

- Generated new signed cert from internal CA, then upgrade

The logs on the server look like this:

2018-02-12T10:42:48.801-06:00 WARN  (0C44-1240) <SwiftMQ-jms.connection-3> [JMSAuthenticationSwiftlet] No certificate presented by user broker/testsrv

2018-02-12T10:42:48.803-06:00 WARN  (0C44-1240) <SwiftMQ-jms.connection-3> [JMSAuthenticationSwiftlet] No certificate presented by user broker/testsrv

2018-02-12T10:42:48.804-06:00 WARN  (0C44-1238) <SwiftMQ-jms.connection-1> [JMSAuthenticationSwiftlet] No certificate presented by user broker/testsrv

2018-02-12T10:42:48.804-06:00 WARN  (0C44-1238) <SwiftMQ-jms.connection-1> [JMSAuthenticationSwiftlet] No certificate presented by user broker/testsrv

2018-02-12T10:42:53.881-06:00 ERROR (1450-168C) <SwiftMQ-ConnectorPool-5> [JMSTunnelSSLSocketFactory] Certificate thumbprint verification failed, no router thumbprints available. Presented identity: router/testsrv

2018-02-12T10:42:53.881-06:00 ERROR (1450-168C) <SwiftMQ-ConnectorPool-5> [JMSTunnelSSLSocketFactory] General error occurred: No known thumbprints: router/testsrv

2018-02-12T10:42:53.965-06:00 ERROR (1450-1688) <SwiftMQ-ConnectorPool-4> [JMSTunnelSSLSocketFactory] Certificate thumbprint verification failed, no router thumbprints available. Presented identity: router/testsrv

2018-02-12T10:42:53.965-06:00 ERROR (1450-1688) <SwiftMQ-ConnectorPool-4> [JMSTunnelSSLSocketFactory] General error occurred: No known thumbprints: router/testsrv

2018-02-12T10:42:54.041-06:00 ERROR (1450-1684) <SwiftMQ-ConnectorPool-3> [JMSTunnelSSLSocketFactory] Certificate thumbprint verification failed, no router thumbprints available. Presented identity: router/testsrv

2018-02-12T10:42:54.041-06:00 ERROR (1450-1684) <SwiftMQ-ConnectorPool-3> [JMSTunnelSSLSocketFactory] General error occurred: No known thumbprints: router/testsrv

2018-02-12T10:42:54.116-06:00 WARN  (0C44-1248) <SwiftMQ-jms.connection-5> [JMSAuthenticationSwiftlet] No certificate presented by user broker/testsrv

2018-02-12T10:42:54.116-06:00 ERROR (1450-16E0) <SwiftMQ-ConnectorPool-6> [JMSTunnelSSLSocketFactory] Certificate thumbprint verification failed, no router thumbprints available. Presented identity: router/testsrv

2018-02-12T10:42:54.116-06:00 ERROR (1450-16E0) <SwiftMQ-ConnectorPool-6> [JMSTunnelSSLSocketFactory] General error occurred: No known thumbprints: router/testsrv

2018-02-12T10:42:54.189-06:00 ERROR (1450-1120) <SwiftMQ-ConnectorPool-1> [JMSTunnelSSLSocketFactory] Certificate thumbprint verification failed, no router thumbprints available. Presented identity: router/testsrv

2018-02-12T10:42:54.189-06:00 ERROR (1450-1120) <SwiftMQ-ConnectorPool-1> [JMSTunnelSSLSocketFactory] General error occurred: No known thumbprints: router/testsrv

2018-02-12T10:42:54.191-06:00 WARN  (0C44-1240) <SwiftMQ-jms.connection-3> [JMSAuthenticationSwiftlet] No certificate presented by user broker/testsrv

2018-02-12T10:42:54.191-06:00 WARN  (0C44-1244) <SwiftMQ-jms.connection-4> [JMSAuthenticationSwiftlet] No certificate presented by user broker/testsrv

2018-02-12T10:42:54.192-06:00 WARN  (0C44-1248) <SwiftMQ-jms.connection-5> [JMSAuthenticationSwiftlet] No certificate presented by user broker/testsrv

2018-02-12T10:42:54.247-06:00 WARN  (0C44-1244) <SwiftMQ-jms.connection-4> [JMSAuthenticationSwiftlet] No certificate presented by user broker/testsrv

2018-02-12T10:42:54.866-06:00 WARN  (1450-16A0) <Thread-2> [bo] Item enqueued on "Outbound JMS Forwarder" but there are no workers available to process it. Busy workers = 0, queue length = 130

Any thoughts on what else we could try that would impact the cert or allow us to regain access to the admin console after an upgrade?

[TechMassey]

Very nice your digging into the logs! The connection server logs will absolutely help us narrow this down.

• Verify the Horizon View Connection Server and Web Component service is running.
• Also, verify the friendly name on your cert is 'VDM'. If it is not, fix it, and then reboot
• My final tip is if you have two connection servers, shut both down. Then start up only one and let it sit to get its services running, then try accessing the again.

Good Luck!

[John_Getzke · Accepted solution]

A coworker worked on the problem for me while I was away yesterday.  He was able to repair the problem by performing a series of uninstalls, reinstalls and restorations of the LDAP DB's between the primary and secondary connection server.  We have successfully completed the 7.4 upgrade in our test environment and will try again in prod in the future.

Thanks for the suggestions though.

[jharrell1]

I'm having the same issue upgrading from 6.2 to 7.4, were you able to find a solution?

[jharrell1]

Good morning all,

I believe we've found a solution for our problem.  Hopefully this will save someone a few days of troubleshooting.

Below are the steps we executed to correct the admin console from not loading:

     1) uninstall some old programs / utilities

               -  HorizonToolbox  ( a vmware labs tool)  <--- i believe this was the conflict

               -  Vmware vsphere client 5.1

     2) reboot

     3) update View connection server

     4) reboot

I've only upgraded a sandbox'd copy of our production environment but i feel confident this will be the fix for us.

We do still have some certificate warnings for the connection server and view composer but there are some KB articles on those issues that are common with this upgrade.

Hope that helps, thanks everyone!

[GAS91]

Hi,

For anyone who still may have this problem, I can confirm that the HorizonToolbox was the problem.

Uninstall HorizonToolbox before upgrade (alternatively, re-install Horizon if you already upgraded).

Tested on VMware Horizon 7.5.1

Thx to jharrell1 for the solution.