Knowledge Base

Search the Knowledge Base:
Products:
Search In:
 

When Upgrading from VirtualCenter 1.x to 2.0.1, Database Upgrades Fail if the 1.x System Has Both an MSDE Database and a Production Database

Details

Why does my database upgrade fail when I upgrade from VirtualCenter 1.x to 2.0.1? I have both an MSDE database and a production database on my system. Could this be part of the problem?

Solution

When the system you are upgrading has both an MSDE database and a production database, the Database Upgrade wizard changes the DSN setting used for VirtualCenter 1.x so that it points to the MSDE database instead of the production database. To avoid this problem, change the DSN setting in the wizard so that it points to the database used for VirtualCenter 1.x. Restart the VirtualCenter 2.0 Server installer, select the Repair/Modify option, and specify the correct DSN setting. Also, uninstall the MSDE database for VirtualCenter.

Keywords

relnotes

Feedback

Rating: 1 - Lowest 2 3 4 5 - Highest (0 Ratings)   

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (2000 or fewer characters)
Submit
Rating: 1 - Lowest 2 3 4 5 - Highest (0 Ratings)   
Actions
  • KB Article: 3438229
  • Updated: Oct 19, 2007
  • Products:
    VMware ESX
    VMware VirtualCenter
  • Product Versions:
    VMware ESX 3.0.x
    VMware VirtualCenter 2.0.x