VMware Communities > VMTN > VMware Infrastructure™ > VI: ESX 3.5 > Discussions
Up to Discussions in VI: ESX 3.5
This thread is locked

This Question is Answered

1 2 3 ... 11 Previous Next
157 Replies Last post: Apr 18, 2008 3:56 PM by Badsah

VI 3.5 Update 1 upgrade experiences

Apr 12, 2008 8:08 AM

Click to view jasonboche's profile Champion jasonboche 5,893 posts since
Jan 7, 2004 Moderator
I upgraded VirtualCenter 2.5.0 to 2.5 Update 1 today (using SQL Server 2005 SP2 back end).

Observations:
1. The license server installation/upgrade is still not called as part of the autorun.exe as all other VI components are (VC server, VC client, VC Update Manager, VMware Converter for VC). The license server installation/upgrade must still be performed as a separate step at the very beginning.

2. SQL back end users are no longer allowed to use the SQL Server 2003 ODBC driver packaged with Windows Server. You must now download and use the SQL Native Client driver and rebuild your DSNs using this driver. Available at: http://www.microsoft.com/downloads/details.aspx?FamilyId=50b97994-8453-4998-8226-fa42ec403d17&DisplayLang=en

3. VMware took the feedback of all the database upgrade issues being had with the release of VC2.5.0. Helpful screens now guide us to the correct database upgrade permissions referencing the applicable VMware KB articles. Furthermore, if by chance you grant your VirtualCenter SQL account the sysadmin role to SQL server, the upgrade picks up on this and presents you with a warning message that a new parallel set of database tables will be created rather than upgrading the existing infrastructure. Failure to correct this situation will essentiall result in losing your datacenter after the upgrade is complete.

4. Database upgrade completed without any issues.

5. Once completed, Help|About reflects VIC and VirtualCenter versions 2.5.0 build 84767. Why not 2.5.1? Why is the incorrect build number of 84767 shown instead of what's listed on VMware's website build 84782






Jason Boche
VMware Communities User Moderator

Re: VI 3.5 Update 1 upgrade experiences Apr 11, 2008 11:48 AM
Click to view RParker's profile Champion RParker 5,270 posts since
Dec 6, 2006

1. The license server installation/upgrade is still not called as part of the autorun.exe as all other VI components are (VC server, VC client, VC Update Manager, VMware Converter for VC). The license server installation/upgrade must still be performed as a separate step at the very beginning.

So does this mean the license server was upgrade with this Update 1 version? I didn't upgrade mine, but I did do a new install of VC 2.5 a couple of months ago.

Re: VI 3.5 Update 1 upgrade experiences Apr 11, 2008 11:50 AM
in response to: RParker
Click to view jasonboche's profile Champion jasonboche 5,893 posts since
Jan 7, 2004 Moderator
I don't know but I'd lean towards doubtful.. I always make it a habit to upgrade it, if only to increment the build version so that it's consistent with the build numbers of the rest of the VC components.






Jason Boche
VMware Communities User Moderator

Re: VI 3.5 Update 1 upgrade experiences Apr 11, 2008 11:59 AM
Click to view jasonboche's profile Champion jasonboche 5,893 posts since
Jan 7, 2004 Moderator
Bug:

In the new VIC, both add on component pugins are installed, but the Converter plugin is no longer enabled (the check box is empty). Clicking the check box to enable it instantly crashes the VIC. This happens on two different machines where I've upgraded the VIC to Update 1. The log file at C:\Documents and Settings\jason\Local Settings\Application Data\VMware\vpx\ has several lines reading "Attempted to read or write protected memory. This is often an indication that other memory is corrupt."

http://communities.vmware.com/servlet/JiveServlet/download/912760-7959/untitled.jpg






Jason Boche
VMware Communities User Moderator
Attachments:
Re: VI 3.5 Update 1 upgrade experiences Apr 11, 2008 12:03 PM
Click to view sbeaver's profile Guru sbeaver 7,718 posts since
Nov 1, 2004 Moderator
All hail Jason the Brave One!!!

Steve Beaver
VMware Communities User Moderator

**Virtualization is a journey, not a project.**

Re: VI 3.5 Update 1 upgrade experiences Apr 11, 2008 12:05 PM
in response to: sbeaver
Click to view jasonboche's profile Champion jasonboche 5,893 posts since
Jan 7, 2004 Moderator
sbeaver wrote:
All hail Jason the Brave One!!!

Steve this was in the lab, not production (I'm sure you think I'm crazy but give me a little credit anyway).






Jason Boche
VMware Communities User Moderator
Re: VI 3.5 Update 1 upgrade experiences Apr 11, 2008 12:25 PM
in response to: jasonboche
Click to view RParker's profile Champion RParker 5,270 posts since
Dec 6, 2006
We didn't have this problem... maybe something was weird with your install.
Re: VI 3.5 Update 1 upgrade experiences Apr 11, 2008 12:26 PM
in response to: jasonboche
Click to view RParker's profile Champion RParker 5,270 posts since
Dec 6, 2006
Ours was production.... :) I don't mind being a guinnea pig, I thrive on it. I am the one that installs/configures the servers anyway, so if they break, I can fix them.
Re: VI 3.5 Update 1 upgrade experiences Apr 11, 2008 12:34 PM
in response to: jasonboche
Click to view jpoling's profile Expert jpoling 444 posts since
May 25, 2004

I ran into the crashing of the VI Client when enabling Enterprise converter as well. . .found a resolution here:

http://www.yellow-bricks.com/2008/02/04/installing-the-converter-plugin-crashes-virtualcenter/

I just renamed the ssleay32.dll and then was able to get converter enabled.

For what it's worth

Jeff

Re: VI 3.5 Update 1 upgrade experiences Apr 11, 2008 12:35 PM
Click to view maguar99's profile Novice maguar99 16 posts since
Oct 8, 2007

Jason,

I saw the same thing, I had already had 2.5.0 installed and downloaded build 2.5.0Update 1 (build 84782). I went through the entire upgrade, and restarted VC, but afterwards, help about had the 2.5.0 build number: (Build 84767) so you are not alone.

Matt

Re: VI 3.5 Update 1 upgrade experiences Apr 11, 2008 12:49 PM
in response to: maguar99
Click to view jasonboche's profile Champion jasonboche 5,893 posts since
Jan 7, 2004 Moderator
maguar99 wrote:

Jason,

I saw the same thing, I had already had 2.5.0 installed and downloaded build 2.5.0Update 1 (build 84782). I went through the entire upgrade, and restarted VC, but afterwards, help about had the 2.5.0 build number: (Build 84767) so you are not alone.

Matt


Well in fairness, nowhere in the documentation did I see it was now 2.5.1 but I was just kind of questioning why not increment the version number to 2.5.1 instead of calling it 2.5 Update 1. The bigger issue is why Help|About shows build 84767 but http://www.vmware.com/download/vi/ shows build number of 84782?

And thanks Jeff for the suggestion about the crashing client. That indeed fixed the crashing issue. reference: http://communities.vmware.com/message/840021#840021

Jas






Jason Boche
VMware Communities User Moderator
Re: VI 3.5 Update 1 upgrade experiences Apr 11, 2008 12:47 PM
in response to: maguar99
Click to view RParker's profile Champion RParker 5,270 posts since
Dec 6, 2006
I saw the same thing, I had already had 2.5.0 installed and downloaded build 2.5.0Update 1 (build 84782). I went through the entire upgrade, and restarted VC, but afterwards, help about had the 2.5.0 build number: (Build 84767) so you are not alone.

The SAME identical thing happened in VC, and I even posted it.. but no one seemed to care. There is a trend here, and it's not good.

VC 2.5 is build 64201 on the website, but it's actually 64192 (help about).

Apparently the same thing with VC 2.5 Update 1. The build does not correspond with the website, there is a miscommunication somewhere...

Re: VI 3.5 Update 1 upgrade experiences Apr 11, 2008 12:53 PM
in response to: RParker
Click to view jasonboche's profile Champion jasonboche 5,893 posts since
Jan 7, 2004 Moderator
I've posted a note on the moderators forum asking them to look into it. Agreed this is not the first time this has happened and we need more quality control on what goes on the website.






Jason Boche
VMware Communities User Moderator
Re: VI 3.5 Update 1 upgrade experiences Apr 11, 2008 1:06 PM
in response to: jasonboche
Click to view java_cat33's profile Master java_cat33 1,202 posts since
Aug 29, 2007
So has anyone of you guinea pigs upgraded ESX to 3.5 Update 1 yet? :D
Re: VI 3.5 Update 1 upgrade experiences Apr 11, 2008 1:23 PM
in response to: java_cat33
Click to view RParker's profile Champion RParker 5,270 posts since
Dec 6, 2006

So has anyone of you guinea pigs upgraded ESX to 3.5 Update 1 yet?

Only on 8 of our 14 machines... ;) The others are upgrading tonight.

1 2 3 ... 11 Previous Next
Actions
Up to Discussions in VI: ESX 3.5