VirtualCenter 2.0.2 Web Interface does not work after upgrade

I ran into an issue at a client several weeks ago where the web interface for VirtualCenter 2.0.2 wasn’t working. They had just upgraded from version 2.0 where it was previously working fine. It’s not a common issue, but if you decide to upgrade to VirtualCenter version 2.02 before going to VirtualCenter 2.5 you might run into it. I had never experienced the problem so it was a surprise to me. Luckily it is well documented and easy to resolve.

After upgrading to VirtualCenter 2.0.2, Update 1, Update 2 or Update 3, the VMware VirtualCenter 2 Welcome page does not render completely is the title of KB 100285 which describes the problem. I was able to folow the instructions in the KB and restore the web interface with no problems. The rest if this post is taken straight from the VMware KB.

Details


After upgrading to VirtualCenter 2.0.2, Update 1, Update 2 or Update 3, the VMware VirtualCenter 2 Welcome home page does not completely render in the browser. The page does not show any text and no links are available. The screen looks similar to the following image:

To solve the issue follow these steps:

  1. Navigate to the following folder: C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\docRoot.
  2. Create a folder called ‘en‘.
  3. Download the attached welcomeRes.zip and extract welcomeRes.js to the newly created folder.

Once this is done, you should be able to properly view the VMware VirtualCenter 2 Welcome page.

Note: This problem only occurs on an upgrade of VirtualCenter, fresh installations are not affected.

You can download the welcomeRes.zip file from the KB Article or I am keeping a copy here at VM /ETC as well.

Download fwelcomeRes.zip

Downloaded a total of 122 times

Related Posts

Tags: , , ,

3 Responses to “VirtualCenter 2.0.2 Web Interface does not work after upgrade”

  1. Eric Siebert Says:

    That’s actually a pretty common one that was first seen right after 2.0.2 Update 1 came out about a year ago. Here’s the Vmtn thread that first identified the problem.

    http://communities.vmware.com/thread/110156

    VMware was aware of the problem right away but it wasn’t fixed until 2.0.2 Update 4.

  2. Rich Says:

    Thanks Eric. I guess it just has not been common for me.

  3. Eric Siebert Says:

    Yeah it bit a lot of people when they tried upgrading after 2.0.2U1 was released. It’s a shame it got past their QA and even more shameful that it took them so long to resolve it. Hopefully they’ve learned from the last time-bomb snafu and implement better QA testing in the future.

Leave a Reply

*
To prove you're a person (not a spam script), type the security word shown in the picture. Click on the picture to hear an audio file of the word.
Click to hear an audio file of the anti-spam word

Subscribe



Add to Google Reader or Homepage
Subscribe in NewsGator Online
Add to netvibes
Add to Plusmo

twitter.com/rbrambley
    Advertisements
    Links