VMware Horizon Community
swathimp
Enthusiast
Enthusiast
Jump to solution

Unable to launch view admin console

Am unable to launch the view administrator console from my connection server.

Error message is "webpage is not available" .

View version is 7. checked with the KB articles. Found the friendly name is vdm. Port 443 is free. Restarted the service and server several times

Can anyone help me with this?

TIA

Reply
0 Kudos
1 Solution

Accepted Solutions
BenFB
Virtuoso
Virtuoso
Jump to solution

If both components are installed and the services are running I would look at the connection server logs for errors. Given your situation if this is a production environment I would be filling an SR with support. This may require a reinstall and restore.

View solution in original post

Reply
0 Kudos
18 Replies
swathimp
Enthusiast
Enthusiast
Jump to solution

The console worked for 2 months. Updated the license in esxi server and then after restart of connection server, it worked once. After that the issue occured.

Reply
0 Kudos
amr12
Enthusiast
Enthusiast
Jump to solution

Is anything else on your connection server using port 443 such as IIS? Which VMware Horizon services are not running?

Reply
0 Kudos
BenFB
Virtuoso
Virtuoso
Jump to solution

Do you have just one or multiple connection servers? All of the connection servers need to be started before the Horizon Administrator page will load.

Reply
0 Kudos
swathimp
Enthusiast
Enthusiast
Jump to solution

No, IIS was not installed.

No other service is using port 443. Checked using command : netstat -ano

Reply
0 Kudos
swathimp
Enthusiast
Enthusiast
Jump to solution

I am using only one connection server in my environment

Reply
0 Kudos
BenFB
Virtuoso
Virtuoso
Jump to solution

At this point we need to look at the connection server logs to determine what is going on. Have you filled an SR?

Reply
0 Kudos
swathimp
Enthusiast
Enthusiast
Jump to solution

Hi Ben, I didn't file an SR yet. The generic solutions provided as per the KB articles are checked. I am looking for any options that could solve this before filing the SR.

Reply
0 Kudos
BenFB
Virtuoso
Virtuoso
Jump to solution

Have you looked at the connection server logs? Is this a new install or did it work previously?

Reply
0 Kudos
swathimp
Enthusiast
Enthusiast
Jump to solution

It was working for 2 months. recently I updated the esxi license and the adcs role which was installed in connection server was removed. I checked the debug logs and found

"Attempting to connect to JMS using tunnel\VM port 4002

Direct JMS connect

could not find pae.jms properties"

Repeatedly and some more logs

Reply
0 Kudos
swathimp
Enthusiast
Enthusiast
Jump to solution

After updating the ESXi licnese I was able to connect only one. I changed the AD password in composer server settings,. Form the next day onwards I was not able to connect

Reply
0 Kudos
BenFB
Virtuoso
Virtuoso
Jump to solution

In Programs and Features on the Connection Server do you see the following installed?

AD LDS Instance VMwareVDMDS

VMware Horizon 7 Connection Server

Reply
0 Kudos
swathimp
Enthusiast
Enthusiast
Jump to solution

Yes, Both are installed

Reply
0 Kudos
BenFB
Virtuoso
Virtuoso
Jump to solution

If both components are installed and the services are running I would look at the connection server logs for errors. Given your situation if this is a production environment I would be filling an SR with support. This may require a reinstall and restore.

Reply
0 Kudos
swathimp
Enthusiast
Enthusiast
Jump to solution

This is not  a production environment.

Reply
0 Kudos
BenFB
Virtuoso
Virtuoso
Jump to solution

What's the hesitation to file an SR? If the environment is non-production just rebuild the servers and the Horizon environment.

Reply
0 Kudos
swathimp
Enthusiast
Enthusiast
Jump to solution

No hesitation in logging a SR. I wanted to look for if  fix is available. I reinstalled the server and it is working now.

Reply
0 Kudos
swathimp
Enthusiast
Enthusiast
Jump to solution

A reinstall fixed the issue

Reply
0 Kudos
swathimp
Enthusiast
Enthusiast
Jump to solution

I have reinstalled the entire environment

Reply
0 Kudos