VC 2.0.2 upgrade stalls with "Please insert the disk: 1"

[urgrue]

I'm trying to upgrade from 2.0.1 to 2.0.2. Everything was going fine until it spontaneously decides to ask "Please insert the disk: 1". I'm tried inserting everything vmware-related I've got into every possible drive, but nothing works.

Anyone have any ideas?

[peetz]

What choices do you have in the "Please insert disk"-box? Is there a "Cancel"-button?

If yes, click it. Hopefully Windows will then ask for the path to a specific file it is looking for. I guess that it looks for the msi-sources of the old version 2.0.1, and if you choose this file then the installation might continue successfully.

You could also try to repair the existing 2.0.1 installation before you try to upgrade to 2.0.2.

\- Andreas

[urgrue]

The options are OK and Cancel. Cancel asks me for confirmation and then exits the entire setup process

I tried also giving it my 2.0.1 CD, but it didn't help....

[peetz]

What install source are you using? Are you sure that it includes all required installation files?

If you downloaded the ISO try downloading it again and/or check the md5sum.

[masaki]

Have a look at this:

http://www.vmware.com/community/thread.jspa?messageID=656925&#656925

and try to change your install path

[urgrue]

That was about vmware tools, didnt seem to apply to me. There is not mention of any drive letters in the registry with regards to virtual center.

However, I did solve this, after a few hours of uninstall/reinstall/etc. This was made even more annoying because a failed upgrade to 2.0.2 corrupts the database. It still works in 2.0.1 but further attempts to install 2.0.2 (even a fresh install using the old database) fails. Basically I had to restore from backups. Also even after uninstalling VC, port 80 is often reserved by IIS, so you have to manually go stop IIS or else VC will refuse to install onto that port since it sees it as reserved.

Finally I got everything to work by:

-uninstall virtual center 2.0.1, and restore db from backups if possible, and kill IIS.

-install 2.0.2. it will fail to start, because it doesnt upgrade the database.

Do this: http://kb.vmware.com/kb/1001680

BUT!!! before running the last MS SQL command, open the mentioned updatedb_mssql.sql,

scroll to the end, and replace "drop view VPXV_HIST_STAT" with "drop table VPXV_HIST_STAT".

After that, everything worked.

[gabilu]

I had the same problem with the installation. I tried what you suggested but it didn't work either. I still get an error while running the last SQL command.

What exactly did you modify in the file ?

[langonej]

Just hosed my working VC 2.0.1 thanks to this install. Now I get to play the uninstall/reinstall/KB article game.

[gladney]

Same thing is happening to me

"please insert disk 1" Ive put in every version of VC that Ive upgraded (3 disks total) and it took nothing. Just for grins I'm re downloading 2.02 iso to try again, before I go though the uninstall/reinstall agony.

If a different iso works Ill inform all (but I seriously doubt it will.)

[gladney]

opps clicking post twice actually posts two messages

Message was edited by:

gladney

[gladney]

I had to go the same route in the end as urgrue, although I skipped his last step and everything seems fine in testing. The KB article 1001680 was followed though.

Hope no one else gets this annoying error as its well... annoying.

[joelgb]

This happened to me as well. I checked the installer log file (vmmsi.log) in the %TEMP% location and found that the installer was looking for "VMware VirtualCenter Server 2.0.msi" in the root of D:\. On the CD I burned from the ISO download, this file is located in D:\bin\.

We have a slow internet link here, so downloading the .zip installer was not an option, I too ended up with a non-working Virtual Center Server. So to work around this in a pinch I ended up copying the contents of the CD to a Flash stick, changing the drive letter of the flash stick and the CD Rom. And copying the .msi file to the root of the flash drive. (I also think I had to copy a .cab file to the root of the flash stick later in the install process).

Note: I also attempted copying the contents of the CD to the machine locally and running the installer from there. However, The log file still showed the installer looking for the .msi on the root of the CD drive.

Maybe this post will save someone in a pinch who can't wait to download the .zip.

[Real_Mr_G]

Goo tip joelgb!

I experienced the same problem ('...insert the disk 1...') so, after reading Joelgb's tip and because I have my VC as a VM, I just added another VMDK disk to it and copied the entire CDROM to the root of the new disk.

I then ran 'bin\VMware VirtualCenter Server 2.0.msi' from the virtual disk and it all ran through smoothly.

I will post here if I experience problems further down the line.

Chris

[JLiebster]

Try the instructions in this recently released KB article:

http://kb.vmware.com/kb/1001900

[DJDaigneault]

Same issue here. After following suggestions posted I now have "failed with error 25014". I am sure I have lost the database and possible have no backup.

What is stored in the DB and what is the consequence of starting with a new DB from scratch?

Thanks,

Dan

[masaki]

What is stored in the DB -> almost ALL

Starting from scratch you'll loose the hierarchical structure (datacenters, hosts, clusters), permissions, HA and DRS, performance data, task and events, scheduled tasks.

You'll not loose the virtual machines and templates. You can import them later.

[DJDaigneault]

Thanks! My environment is very small with only 8 VM's. Recreating should be easy and quicker than trying recovery.

I do have an image of this system from Sunday evening but don't know how to selectively restore VC DB...

Dan

[masaki]

If you don't care about performance data I sugest you to start from scratch.

Otherwise good luck!

[mvarre]

This is absolutely horrible. Obviously this is a known issue and VMWare is still releasing this as-is. I'm sick of application developers spending more time on adding new features instead of fixing stuff that doesnt work as advertised!