vSphere Web Access - Web Service not available

[nbuache1]

Hello!

I've upgraded ESX & VC to vSphere 4.0. Everything is now working fine, except vSphere Web Access.

The first page displays correctly, but after inserting the credentials I'm getting the message "Web Service not available".

As I've IIS installed on this servers for some others tools, HTTP port has been modified to port 81.

I found two documents on the web, but it didn't help me (these settings worked before the upgrade, but not after):

http://www.vmware.com/support/vsphere4/doc/vsp_esx40_vc40_rel_notes.html

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

Do you have any idea? Where should I check/modify this port?

Or is there a way to force it to only use HTTPS? This could maybe resolve my issue.

Thanks for your help!

Nicolas

[a2alpha]

Hi Nicolas,

VMware have disabled WebAccess by default in vSphere:

Try this document:

Specifically:

*

Run the vSphere Web Access Service on vCenter Server*

You must run the vSphere Web Access service on vCenter Server before you use your Web browser to connect.

If the service is not currently running, you cannot log in.My Computer* and select Manage.*

The Computer Management window appears.

*2 Expand Services and Applications and select Services.*

3 Locate VMware VirtualCenter Management Webservices on the list and check whether the service is running.

*4 If the service is not running, right-click VMware VirtualCenter Management Webservices and select *Start.

*

If it is ESX then try here:

Hope this helps,

Dan

[nbuache1]

Dear Dan,

Thanks for your reply, but the service is running.

I'm able to get the first page (where you can install the VC Client or click to access the web console). When I click on the web access console, it's asking the login/password informations then it's failing withthe error message "web service not available"

[athlon_crazy]

Seem, I'm not the only one who having this problem when you changed the default port (80) to another one.!

http://communities.vmware.com/thread/235302?tstart=0

vcbMC-1.0.6 Beta

vcbMC-1.0.7 Lite

[ElioteArg]

Hi!

I have VMware Server 2.0.2 and VMware vCenter Server 4.0 installed on the same host and I cannot make the "VMware Server Web Access" service and "VMware VirtualCenter Management Webservices" work simultaneously. Both services use Tomcat6 as I could see. If one service is running, the other one terminates after some minutes of having started it. Apart from that, if ONLY the "VMware VirtualCenter Management Webservices" is running ("VMware Server Web Access" is NOT running), I cannot log in to Web Access (vCenter).

Any idea?

[russjar]

I've got the same issue. I can open the default web page NP https://server_name and open every link on that page EXECPT for "Log in to Web Access" which comes up with an http 404 error. I've confirmed that the installation used default ports, and have confirmed Tomcat6 is bound to the WebManagement Service. If I browse to http://server_name:8443 I go to the tomcat management page.

Idea's...?

Thanks all in advance

VCP,MCSE NT4/W2k/W2k3, MCSA W2k3

[DonChino]

I guess I will come out of "retirement" and grab me some points although I never really get any points, since I usually post solutions without responding to questions. Anyway, I have your answer because this is something that tripped me up before and then this past weekend it happened again and I decided to just search and help any other lost souls.

Solution? Quite stupid actually.

Basically it looks like the client gets tripped up during some update because I had Update Manager running and then I had updated my ESXi boxes before, so everything seems to work fine but sometimes you will get this weird error. You can access the web page from the host server itself but you cannot log in because you get "Web Service not available" but then you can still see the clusters and hosts defined within vCenter but you cannot connect with Client or Web. The following steps are for the vCenter Host Server:

Basically leave everything alone.

UNINSTALL the vSphere client.

Reboot.

Then go to web interface on host machine http://localhost or http://127.0.0.1

Click on DOWNLOAD vSphere Client

Install the client.

Then try connecting.

WHAM!!! It connects. Not sure why but I am guessing that vCenter gets updated or something and then the client is not able to re-connect and I had the client installed from before and on another machine. Not sure if maybe I had the wrong version but if you install from the version provided by vCenter then it works. All I care is that I am able to connect again...

Good Luck...

Now give me points...

:smileylaugh: