VC 2.5 upgrade - WIPED MY DATABASE!

[eric_kufrin]

Upgrading to VC 2.5 wiped my database!!

I bring up VC and ALL OF MY HOSTS AND CONFIGURATION IS GONE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

I am so mad right now!

This is the second time a VC update has wiped my database!

Seriously, WTF!

[margitza]

Checkout the following solution, it works fine with our installation.

1. Restore the backup of the database.

2. Ensure all the permissions are set correctly as per KB

3. Delete the following jobs from SQL Manager ( these can be found under ) Management./SQL Server Agent/Jobs

• Past Day Stats Rollup

• Past Week Stats Rollup

• Past Month Stats Rollup

4. Uninstall and Reinstall VC.

Greetings

[Byron_Zhao]

Before the VC2.5 upgrade, I did lots of research on the this forum and reading the documentations. Finally, the upgrade went through fine without wiping out the database. However, I ran into a HA error problem on 80 percent of my hosts.

• One host's service console lost network connection. After stopping firewall, restarting hostd, everything starts working fine.

• One host's hostd stop when after it upgrade VC agent. Need to manually brought up hostd.

• HA agents errors happens many hosts, needed to turned HA off for quite a long time before I could turn them back on into a stable status.

Anyway, it is all good now, except the warning message for the management network redundancy.

-BZ

[rameredit]

Because the VC install does not (cannot) add jobs due to the lack of the SQL Server Agent, how does one go about scheduling these? Are the SQL scripts already on the machine from the install?

[mats82]

I feel for you!! I did a similar thing by changing sysadmin access on the db user, which created a new parallel DB.

Lesson is? DO A BACKUP BEFORE STARTING!!

[Mark_P_Werner]

Well I am not upgrading from anything. I am trying to perform a brand new, fresh install.

Trying to get VC 2.5 to install.

VC database SQL login user has db_owners rights to VC DB and MSDB DB (and no other permissions or rights).

.NET Framwork on system installing VC is 2.0.

MDAC on system installing VC is 2.8 SP1.

When testing System DSN DB connection on system installing VC it tests successfully.

System installing VC on is XP (tried more than one machine).

SQL Server is 2000 SP4

Database Recovery Model changed from Full to Bulk-Logged.

When trying to install VC the following error message appears.

"The DB user entered does not have the required permissions needed to install and configure VMware VirtualCenter Server with the selected DB. Please see the installation documentation for detailed DB permission requirements."

This is not an upgrade and I receive the error. This is a brand new, fresh install, that has been attempted on several machines now. That said, the information in the Release Notes and Known Issues is not the problem or the resolution. The information in the KB articles is not the solution as it is not applicable, and everything is configured just as it should be according to VMware.

Any ideas?

Thanks!

[greendxr]

We ran in to this problem while upgrading to VC 2.5. Thanks to this thread I learned that the problem was with us using the NT account for a remote SQL connection. Rather than change the setup we opened a ticket with vmware support and were able to resolve this issue. The recommendation that we received was to change the NT account's password to a non-alphanumeric password. Below are the instructions that we followed which worked and allowed us to continue with the upgrade.

-Change the password on the account used, test it with VirtualCenter first (before upgrading)

-Once that is working you can try and do the upgrade again.

-In order to change the database password that Virtual Center uses please follow the steps below.

Stop the Virtual Center Service

1. Start > Control Panel > Administrative Tools > Services.

2. Select the "VMware VirtualCenter Server" service.

3. Right click and select "Stop"

Once the service has stopped users will not be able to connect to your Virtual Center Server, however this will not affect running virtual machines.

1. Open a command prompt.

2. Navigate to the folder which contains the VirtualCenter program files.

3. Run the command "vpxd.exe -p".

4. Enter the new password when prompted.

Return to the Services application and start the "VMware VirtualCenter Server" service once more.