VMware

This Question is Possibly Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
6 Replies Last post: Sep 10, 2007 1:29 AM by PerryWhittle  

VirtualCenter 2.0.2 Build 50618 with a remote SQL 2005 SP2 database. posted: Sep 6, 2007 12:20 PM

Click to view MC1903's profile Enthusiast 44 posts since
Sep 20, 2005
Hi,

I am unable to get VirtualCenter 2.0.2 Build 50618 to connect to a remote SQL 2005 SP2 database. I am using a SQL account for authentication.

The SQL server is Windows 2003 Standard SP2 and the VC server is Windows 2003 R2 Standard SP2. Both servers are running the latest MS security fixes.

I am not using the Native SQL Client - I know that is not supported...

When I run the VC server service interactively, I get the following output:

[code][2007-09-06 16:46:04.221 'App' 3184 info] Current working directory: C:\Program Files\VMware\VMware VirtualCenter 2.0
[2007-09-06 16:46:04.221 'App' 3184 info] Initializing SSL context
[2007-09-06 16:46:04.565 'App' 3184 info] Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 120000000
[2007-09-06 16:46:04.565 'BaseLibs' 3184 info] NFC connection accept timeout: 180000 milliseconds

[2007-09-06 16:46:04.565 'BaseLibs' 3184 info] NFC request timeout: 180000 milliseconds

[2007-09-06 16:46:04.565 'BaseLibs' 3184 info] NFC read timeout: 60000 milliseconds

[2007-09-06 16:46:04.565 'BaseLibs' 3184 info] NFC write timeout: 600000 milliseconds

[2007-09-06 16:46:04.565 'App' 3184 info] Starting VMware VirtualCenter 2.0.2 build-50618
[2007-09-06 16:46:04.565 'App' 3184 info] Account name: SVC_VC2
[2007-09-06 16:46:04.565 'App' 3184 info] [VpxOsLayer] Enabled low-frag process heap.

[2007-09-06 16:46:04.565 'App' 3184 info] [VpxOsLayer] Enabled low-frag crt heap.

[2007-09-06 16:46:04.565 'App' 3184 info] [VpxLRO] 34 max LROs
[2007-09-06 16:46:04.565 'App' 3184 info] [VpxLRO] 6 reserved internal LROs
[2007-09-06 16:46:04.565 'App' 3184 info] [VpxLRO] 6 reserved blocker LROs
[2007-09-06 16:46:04.565 'App' 3184 info] [VpxLRO] 6 reserved short LROs
[2007-09-06 16:46:04.565 'App' 3184 info] [VpxLRO] 4 reserved long LROs
[2007-09-06 16:46:04.565 'App' 3184 info] [VpxLRO] 600-second task lifetime
[2007-09-06 16:46:09.690 'App' 3184 error] [VpxdVdb] Failed to init tableDef: Column VER_ID does not exist in table VPX_VERSION. Database version may be incompatible.
[2007-09-06 16:46:09.690 'App' 3184 error] Failed to intialize VMware VirtualCenter. Shutting down...[/code]

The installer connected to the database and created the tables without error, so I am confused by the service failure and the "Database version may be incompatible" mentioned on second to last line.

If SQL 2005 SP2 is NOT supported, what SQL 2005 SP level is?

Any thoughts/ideas/comments..?

Cheers,

Martin
Click to view Rob.Bohmann's profile Master 583 posts since
May 31, 2005
There is a knowledge base article that apparently is referring to VC 2.01 but it most likely applies to your situation also, at least it is worth checking out.

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=6565318&sliceId=1&docTypeID=DT_KB_1_1&dialogID=20315915&stateId=0%200%2020313452

basically this is the gist of it
This condition can occur if VirtualCenter Server was installed using a database login mapped to a user other than dbo. When the VirtualCenter login is the owner of the database, the login automatically maps to the dbo user.
Click to view esiebert7625's profile Guru 6,794 posts since
Oct 23, 2006
Vcuser is simply the account used by VC to connect to the SQL server database. What type of authentication do you have setup on your SQL server? Is is SQL, Windows or Mixed?
Click to view PerryWhittle's profile Hot Shot 143 posts since
Aug 13, 2007
the login failed is either username or password. Remember that SQL 2005 is now case sensitive by default. When you set the password for the database user did you use upper, lower or mixed case characters?

check your password and then test by opening the DSN connection and put in the username and password. can you proceed to the next screen where you set default database,etc or do you get login failed there?
Click to view PerryWhittle's profile Hot Shot 143 posts since
Aug 13, 2007
the user was a SQL user not Windows...

thats what i expected, also why i posted the comments above. As i said SQL2005 is case sensitive and its catching everybody out at the moment. Simply resetting the SQL users password may have cured your problem

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities