VMware Cloud Community
ezhosting
Contributor
Contributor

Upgrading from ESX 3.5 to Update 2 problems

HI, I am trying to upgrade my datacenter to Update 2,

It consists of the following:

1 x virtual center

2 x ESX servers

I heard it is the smartest to upgrade the VC first?

So I do that, but when I run the installer, and after typing my username and password I get an error like "The wizzard was interrupted, please run the installation again", I tried it several times, but no go.

Question also, when I upgrade one esx host to update 2, will it be able to talk with the esx server that is not update 2 yet? So that I can move my VMs without any downtime?

Greetings,

Reply
0 Kudos
11 Replies
Petter_Lindgren
Contributor
Contributor

I had the same problem and it turned out it was because I was missing msvcr71.dll.

Copy VMware-VIMSetup-2.5.0-104263\updateManager\msvcr71.dll to C:\WINDOWS\System32.

Yes, you should be able to VMotion across the ESX servers.

Reply
0 Kudos
ezhosting
Contributor
Contributor

This worked, thanks!

Reply
0 Kudos
mokotoe21
Enthusiast
Enthusiast

Can you tell us which dialog window you were seeing this message: "The wizard was interrupted, please run the installation again"

Was it during the installation of VC, Update Manager, Converter Enterprise, etc.?

Thanks,

Michael

Reply
0 Kudos
ezhosting
Contributor
Contributor

It happened right after i Selected username and password for the VC, no matter what I choose, I tried not to choose the update manager nor the converter software, It still was there

Reply
0 Kudos
aviwollman
Contributor
Contributor

i've looked in the esx-3.5.0_Update_2-103908 and i can't find the msvc*.dll (or any dll that is).

i found it on the net and it solved the upgrade.

Reply
0 Kudos
ezhosting
Contributor
Contributor

It was no in that location, I had to search the directory and found it in a .cab file

Reply
0 Kudos
loosechange
Contributor
Contributor

Had the identical problem today. Copied the DLL and all worked fine. Love the error message with no details...

Thanks,

Stephen

Reply
0 Kudos
gzulauf
Contributor
Contributor

I had this same problem and copying the dll over fixed it.

Reply
0 Kudos
vmpowered
Enthusiast
Enthusiast

where did you copy the dll files to, under each sub directory

Reply
0 Kudos
gzulauf
Contributor
Contributor

I copied it to C:\Windows\System32

Reply
0 Kudos
vmpowered
Enthusiast
Enthusiast

Thank you for your time, If I would have paid attention I would have found

the answer in the actual post. But again thaks for your time in replying.

bret

Reply
0 Kudos