DiXingyu
Contributor
Contributor

Failed to open the Horizon view admin page

Jump to solution

My server is Windows Server 2012R2, after finished the Horizon View 7 server install, couldn't open the Horizon view admin page. I check the netstat, and the port 443 didn't opened.

Check the vdm log in the /programdata/vmware/vmd/logs, a lot of warning in the log files.

I tried the Windows Server 2008R2, tried the Horizon View 6.2, and the warning is same.

The warning information is below, and I upload the log file.

2017-02-20T07:54:09.518+08:00 INFO  (0C8C-0FEC) <SwiftMQ-ConnectorPool-1> [CertificateUtils] Adding bouncy castle security provider

2017-02-20T07:54:09.674+08:00 WARN  (0C8C-0FEC) <SwiftMQ-ConnectorPool-1> [JMSTunnelSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:09.768+08:00 WARN  (0C8C-0FEC) <SwiftMQ-ConnectorPool-1> [JMSTunnelSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:09.815+08:00 WARN  (0C8C-0C60) <SwiftMQ-ConnectorPool-2> [JMSTunnelSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:09.877+08:00 WARN  (0C8C-0FEC) <SwiftMQ-ConnectorPool-1> [JMSTunnelSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:09.924+08:00 WARN  (0C8C-0304) <SwiftMQ-ConnectorPool-3> [JMSTunnelSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:13.565+08:00 INFO  (0DB8-0DB0) <localhost-startStop-1> [BrokerMessageSecurity] Changing message security mode to: ENHANCED

2017-02-20T07:54:13.565+08:00 INFO  (0DB8-0DB0) <localhost-startStop-1> [BrokerMessageSecurity] Generating new broker message security keys

2017-02-20T07:54:13.565+08:00 INFO  (0DB8-0DB0) <localhost-startStop-1> [BrokerMessageSecurity] Switching message security ENHANCED by default

2017-02-20T07:54:14.221+08:00 INFO  (0DB8-0CEC) <SwiftMQ-ConnectorPool-1> [CertificateUtils] Adding bouncy castle security provider

2017-02-20T07:54:14.284+08:00 WARN  (0DB8-0CEC) <SwiftMQ-ConnectorPool-1> [BrokerSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:14.924+08:00 WARN  (0C8C-0FEC) <SwiftMQ-ConnectorPool-1> [JMSTunnelSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:14.971+08:00 WARN  (0C8C-04F4) <SwiftMQ-ConnectorPool-5> [JMSTunnelSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:15.018+08:00 WARN  (0C8C-08D4) <SwiftMQ-ConnectorPool-6> [JMSTunnelSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:15.065+08:00 WARN  (0C8C-0304) <SwiftMQ-ConnectorPool-3> [JMSTunnelSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:15.112+08:00 WARN  (0C8C-0358) <SwiftMQ-ConnectorPool-4> [JMSTunnelSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:15.315+08:00 WARN  (0DB8-0D48) <TrackerJMSReceiver> [CommonCertificateManager] Found certificate with incorrect identity, deleting: #1e1a00620072006f006b00650072002f00760063006f006e005f0031

2017-02-20T07:54:15.596+08:00 WARN  (0DB8-06A0) <SwiftMQ-ConnectorPool-2> [BrokerSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:16.596+08:00 WARN  (0DB8-0D48) <TrackerJMSReceiver> [CommonCertificateManager] Found certificate with incorrect identity, deleting: #1e1a00620072006f006b00650072002f00760063006f006e005f0031

2017-02-20T07:54:16.800+08:00 WARN  (0DB8-06A0) <SwiftMQ-ConnectorPool-2> [BrokerSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:17.800+08:00 WARN  (0DB8-0D48) <TrackerJMSReceiver> [CommonCertificateManager] Found certificate with incorrect identity, deleting: #1e1a00620072006f006b00650072002f00760063006f006e005f0031

2017-02-20T07:54:18.034+08:00 WARN  (0DB8-06A0) <SwiftMQ-ConnectorPool-2> [BrokerSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

2017-02-20T07:54:19.034+08:00 WARN  (0DB8-0D48) <TrackerJMSReceiver> [CommonCertificateManager] Found certificate with incorrect identity, deleting: #1e1a00620072006f006b00650072002f00760063006f006e005f0031

2017-02-20T07:54:19.393+08:00 WARN  (0DB8-06A0) <SwiftMQ-ConnectorPool-2> [BrokerSSLSocketFactory] Badly formatted identity presented: #1e1a0072006f0075007400650072002f00760063006f006e005f0031

0 Kudos
1 Solution

Accepted Solutions
DiXingyu
Contributor
Contributor

HAHA,I fix the problem, just change the view connect server's name, change it from VCON_1 to VCON1, it's ok

Thank you everyone to reply the question

View solution in original post

3 Replies
ArnoM
Enthusiast
Enthusiast

Have you looked at these KB's?

Launching the VMware View Manager Administration page fails with the error: Internet Explorer cannot...

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=20012...

Also check the locked.properties file  in the conf folder located at C:\Program Files\VMware\VMware View\Server\sslgateway\ on the Connection Server.

This causes the Security Server to fail to read the new SSL certificate.

Blog: https://arnomeijroos.com/ Twitter: @ACMeijroos
0 Kudos
pari2k3
VMware Employee
VMware Employee

See this KB Cannot access the VMware View Admin page (2030824) | VMware KB

Also, it would be helpful if you check the Connection Server debug log and share the details

0 Kudos
DiXingyu
Contributor
Contributor

HAHA,I fix the problem, just change the view connect server's name, change it from VCON_1 to VCON1, it's ok

Thank you everyone to reply the question