vSphere Web Client build number and update issue

[OFURZ]

Hi,

yesterday I did an update of my vCenter (and all the components that belong to it) to the most recent version (5.5 U2d). I was just wondering, wheather my Web Client Server did update successful, because I still have the following error that should already been fixed by 5.5 U1:

IBM Error 2036 using Web Client plug-in - United States

When I look at my Web Client it says: Version 5.5.0 Build 1441077

When I look at Programs and Features it says that version 5.5.0.14567 is installed.

Is that really the most recent build? Unfortunately I did not note the build number before the update, but when I look at the article above, I guess that this is still a build from before 5.5. U1.

Can anyone tell me the most recent build number of vSphere Web Client? I could not find it in the web. Did anyone have similar issues?

Thank You!

[vThinkBeyondVM]

This is the windows vCenter build number :2442328 for VC 55u2d   (Release notes: vCenter Server 5.5 Update 2d Release Notes))

Inside above build package, there use to be web client build as well. From web client about page you should see build number:Version 5.5.0 build 2414847.

Simple install option will install web client automatically. Otherwise you can install web client individually.

Once you download 2442328, it will have web client build as well: https://my.vmware.com/group/vmware/details?downloadGroup=VC55U2D&productId=353&rPId=6994?vmw_so_vex_...

2442330 This is the vCenter appliance build number and it will also have same web client build bundled ie. Version 5.5.0 build 2414847.

Let me know if you want any other info.

[OFURZ]

Thank you vickyvision2020!

Quite strange! :smileyconfused: I did the individual installation, but I can see from Windows Programs and Features that I indeed have installed the Web Client Update. It displays the installation date from yesterday and Version 5.5.0.14567. I guess I will have to uninstall and reinstall web client.

[vThinkBeyondVM]

Before going for re-installation. can you please let me know what is build number shown in web client about page ("https://<Web client VM IP>:9443 "login to web client  username: administrator@vsphere.local ) If you have installed All VC component in the same machine, then use that VM IP in above URL to login web client.

[OFURZ]

Even after uninstall and reinstall, I still got the wrong build number. :smileyconfused:

[vThinkBeyondVM]

The version number that you are getting for web client from programs and features is correct for VC55u2d .ie.. Version 5.5.0.14567. So its latest already. In fact, this is build version number and the one I told in last update is web client build number. Build version number is the one used internally in the windows registry also. If you are upgrading your environment, build version number that you see from programs and features will be checked to decide whether upgrade is required or not. if existing build version number (from programs and features ) is lower that the build version number of the build you are installing then upgrade is required. Otherwise you are already on the latest.

I hope you got this difference.

Just confirm the build number from web client now. If its same as the one I have mentioned( most probably it should be same).

[OFURZ]

At the Web Client about page it says Version 5.5.0 Build 1441077, before and after reinstallation. I guess will ask VMware Support for help.

[vThinkBeyondVM]

I checked in my environment and if you get Version 5.5.0 Build 1441077 from web client about page then build version number corresponding  to it is 5.5.19839.

This web client build Version 5.5.0 Build 1441077 was shipped with VC 5.5 0b  (Release notes: vCenter Server 5.5.0b Release Notes))

are you sure you are log in to the correct web client & not the one which is installed as part of VC 5.5 0b?

[OFURZ]

We only have one vCenter and Web Client. It's not possible to log in to a wrong one. It's really strange. I was also already doubting my sanity. ^^ VC 5.5 0b was the version before the update. I have attached a picture. I will open a ticket at vmware next week and update this thread when I got news.

[vThinkBeyondVM]

This is strange. All right let me know the SR number once you open ticket with VMware.

[OFURZ]

OK, solved. I did a restart of the windows machine running vCenter and Web Client right after the Update, but for any reason the right build number was not displayed until today. Actually I did a restart of the machine where I browsed the Web Client as well, but maybe it has to do with browser cache or anything like that.

Now I see the correct build number and the error for TSM Data Protection plug-in is gone.