Vcenter Upgrade issues from 4.1 to 4.1 Update1

[BT08]

Hi All,

Yesterday I have applied the U1 for VCenter. While the upgrade did finish without any error, some of the things in VCenter is now broken:

1) Storage management service (sms) was red and per logs it could not initialize. It was trying to access to http://localhost/sms/smService-web/health.xml. After changing the URL in C:\Program Files\VMware\Infrastructure\VirtualCenter Server\extensions\com.vmware.vim.sms\extension.xml to https://localhos:8443/... , this started working again.

2) 'storage views' tab. It was working before the upgrade. I know this is similar to the issue above but I cannot locate any xml file to change it. Per viclient log,

WebException occured  in Update : System.Net.WebException: The request failed with HTTP status 503: Service Unavailable.

WebException occured in QueryTopology : System.Net.WebException: The request failed with HTTP status 503: Service Unavailable.

WebException occured  in QueryList : System.Net.WebException: The request failed with HTTP status 503: Service Unavailable.

I believe it is probably using port 80. Do you know which file it is trying to access?

3) "licensing reporting manager" is not working either. When clicked, I get Script Error pop up

When I click yes or no:

Then I get

Authentication required error in the licensing manager window.

Is there a way to change this URL too?

4) The last issue I have is that when I go to Vcenter page, http://vcenter, and click on web access I get redirected to http://vcenter/ui with 503 error. Web access is working fine if I use https://localhost:8443/ui. Any ideas what I can do to fix this?

We have used default ports for everything. The server is 2008 R2 with 2008 SQL SE installed on the same server.

I appreaciate any help.

Thank you.

[alefestaedist]

I suppose you still in this situation:

The upgrade itself was fine no error message and everything else apart from this and the "Storage Management Service" is stuck on "service initializing"

restarting the web service service still the same problem.

So did you try to stop all services set them to "manual startup" thant reboot the server and start them one by one?

The idea is to find what is that is lock the service.

Alex

[Generious]

Hi Alex,

That has been done as well, but I will shedule a restart of the VC server later on this can't at the moment.

Thanks

Kevin

[BT08]

Hi Generious,

I had a similar issue when I first upgraded. Can you first try stopping converter services and restarting SMS (web services)? This had resolved SMS initialization issue until I restarted the server. Then I thought there is a port conflict and reinstalled converter and update manager. BTW, before reinstalling I have uninstalled all versions of Converter. The old version was still registered in Add/Remove programs. After reinstalling, SMS started successfully in my case but this time I was getting localhost:80 problem that I mentioned earlier. Hope this helps.

Thanks.

[Generious]

Hi BT08,

Thanks for the information I noticed a converter PID was on port 80 when I tried to upgrade it, killed the process and it worked fine again and the services are all okay.

So all that remains is the issue with the Licensing Reporting Manager now.

Thanks Again

Kevin

[BT08]

I am just curious, is "storage views" still working?

[BT08]

If you dont mind, one more question, our web access link, although we are not using, is also broken. Have you tested yours as well? If I go to Vcenter home page (https://vcenter) and click  on "Log in to web access", I get redirected to https://vcenter/ui with 503 error. It is working over 8443 though. I am trying to figure if this is also a common issue with the upgrade.

[Generious]

Hi,

Just had a look at the storage views this isn't working.

ref the webaccess this is working fine on my end and I can see the portal and login no problem.

The issue that I'm looking at is the licensing piece.

Going to reboot all of it later on tonight.

[alefestaedist]

well in the vSphere administration guide the error is

"Browser Service Unavailable Error 503

Your browser might show an error saying that the vSphere Web Access service is unavailable.

Problem

vSphere Web Access does not open and the browser shows the

503 Service Unavailable error.

The vSphere Web Access service on the ESX host or vCenter Server is not configured to run automatically or

failed to start properly.

Solution

Start vSphere Web Access service on your ESX host or vCenter Server instance."

that is weird but could be an hardening of the server?  I mean like if you got the webservice that is not really running.

[Generious]

Well I rebooted the active node this evening and started the services one by one same problem on this node.

I used clonezilla on the passive node and updated it to 4.1 Update 1 and started it straight after the upgrade and guess what no issues at all...

So tomorrow night.

Uninstall vCenter on the active node

Delete all the registry keys relating to it and cleanup left over files and folders on it.

Reinstall VC on it.

Our vCenter nodes are clustered up I always wait a couple of days before upgrading the secondary node just in case these types of issues appear

[Mari0]

I have exactly the same problem. Service unavailable on port 80 but working on port 8443. Did you find a fix?

[BT08]

Unfortunately, I could not find a fix for it yet.

[Generious]

In my case I ended up re-installing vCenter on both nodes but I do not consider this a solution at all.

If you don't have a clustered setup this means downtime if you have support teams connecting to vsphere on a daily basis.

[Mari0]

Fixed!

When you try to log in to VMware Virtual Infrastructure WebAccess when a custom Tomcat Webservice port has been specified (whether during installation, before an upgrade, or after), the error 503 Service Unavailable is shown.

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

I changed port 8086 to 8080

Before...

<e id="10">
      <_type>vim.ProxyService.LocalServiceSpec</_type>
      <accessMode>httpsWithRedirect</accessMode>
      <port>8086</port>
      <serverNamespace>/ui</serverNamespace>
    </e>

After...

<e id="10">
      <_type>vim.ProxyService.LocalServiceSpec</_type>
      <accessMode>httpsWithRedirect</accessMode>
      <port>8080</port>
      <serverNamespace>/ui</serverNamespace>
    </e>

🙂

Mario

[antgir1]

Hi to All,

Licensing Reporting Manager Authentication Required bug fix and work around:

I just finish to discuss with vmware support. Here's how to do work around.

1-  Go over this path on your vcenter server 4.1 U1

C:\Program Files\VMware\Infrastructure\tomcat\webapps\license-ui

2- Edit the file "scriptConfig" xml

3-  Put comment around the line "<useInternalSSLProxy>true</useInternalSSLProxy>"

ex: <!-- <useInternalSSLProxy>true</useInternalSSLProxy> -->

This will have effect to says at Licensing Reporting Manager to not used proxy to get informations.

4-Save the file and re-open vSphere Client, (mabe have to accept certificate) and Licensing Reporting manager should work again.

Regards