vCenter

Having just installed 2 3.0.1 hosts for my client I have now come to install their management server.

The only SQL server available to us is a SQL 2005 SP2 server.

The vc database was created fine and the vc installation worked fine with no problems.

Examing the database with 2005 studio manager I could see all the vc tables within the database which was great.

However, when I came to start the vc server service it failed.

Examinging the vpx log files on the vc server showed very strange errors such as execute permission errors, SP_COLUMNS errors etc.

I would have put more details but I don't have access to the vpx logs at the moment.

Has anybody got VC2.0.1 working with SQL 2005 SP2 and if so how?

This article may be applicable:

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=6565318

That's the kb article i followed to setup the database, thanks for replying though!

Anybody else??

This is the contents of one of the vpx log files on the virtual center server

Log for VMware VirtualCenter, pid=4880, version=2.0.1, build=build-32042, option=Release, section=2

\[2007-04-17 16:41:24.784 'App' 5016 info] Current working directory: C:\WINNT\system32

\[2007-04-17 16:41:24.784 'App' 5016 info] Initializing SSL context

\[2007-04-17 16:41:25.628 'App' 5016 info] Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 120000000

\[2007-04-17 16:41:25.628 'BaseLibs' 5016 info] NFC connection accept timeout: 180000 milliseconds

\[2007-04-17 16:41:25.628 'BaseLibs' 5016 info] NFC request timeout: 180000 milliseconds

\[2007-04-17 16:41:25.628 'BaseLibs' 5016 info] NFC read timeout: 60000 milliseconds

\[2007-04-17 16:41:25.628 'BaseLibs' 5016 info] NFC write timeout: 600000 milliseconds

\[2007-04-17 16:41:25.628 'App' 5016 info] Starting VMware VirtualCenter 2.0.1 build-32042

\[2007-04-17 16:41:25.628 'App' 5016 info] Account name: SYSTEM

\[2007-04-17 16:41:25.628 'App' 5016 info] \[VpxOsLayer] Enabled low-frag process heap.

\[2007-04-17 16:41:25.628 'App' 5016 info] \[VpxOsLayer] Enabled low-frag crt heap.

\[2007-04-17 16:41:25.628 'App' 5016 info] \[VpxLRO] 32 max LROs

\[2007-04-17 16:41:25.628 'App' 5016 info] \[VpxLRO] 6 reserved internal LROs

\[2007-04-17 16:41:25.628 'App' 5016 info] \[VpxLRO] 6 reserved blocker LROs

\[2007-04-17 16:41:25.628 'App' 5016 info] \[VpxLRO] 6 reserved short LROs

\[2007-04-17 16:41:25.628 'App' 5016 info] \[VpxLRO] 2 reserved long LROs

\[2007-04-17 16:41:25.628 'App' 5016 info] \[VpxLRO] 600-second task lifetime

\[2007-04-17 16:41:31.003 'App' 5016 error] \[VpxdVdb] Failed to init tableDef: ODBC error: (42000) - \[Microsoft]\[ODBC SQL Server Driver]\[SQL Server]The EXECUTE permission was denied on the object 'sp_columns', database 'mssqlsystemresource', schema 'sys'.. Database version may be incompatible.

\[2007-04-17 16:41:31.003 'App' 5016 error] Failed to intialize VMware VirtualCenter. Shutting down...

\[2007-04-17 16:41:31.003 'App' 5016 info] Shutting down VMware VirtualCenter now

\[2007-04-17 16:41:31.003 'App' 5016 error] SetServiceStatus failed: The handle is invalid

Are you sure the user account that VC is using to login to SQL is the db owner of that database? Maybe try turning the Trustworthy property on.

http://msdn2.microsoft.com/en-us/library/ms187861.aspx

I had the exact same problem: VC2 Patch 2 with SQL 2005 SP2.

I uninstalled VC, deleted my Database, recreated my database following the article you provided Dave.Mishchenko, installed VC2 and it worked well !

Thank you very much !

Hi,

Any idea if SP2 is now supported by VMware?

Thanks

Srinivas

no not yet. i created a SR about 3 weeks ago and they said no.

did this ever get resolved?

SQL2005 SP2 is not supported. Maybe this is one of the reasons why? Not sure myself as we are still on SQL 2000; I did not get a good feeling about the SQL 2005 support.

no, this never got resolved. I did raise a support call with VMware who predictably told me that SP2 wasn't supported. There solution was to revert the SQL install to SP1 (which we couldn't do) or install VC into another database.

In the end we scratched around and managed to find an SQL 2000 SP4 database which of course worked first time.

I've done it, I had to follow the requirements for the SQL server 2005 and it works but I did not have the same error as you...

Hi Skippy,

Do you mean to say you have installed VC database on Sql 2005 SP2 and didn't see any issues?.

I have SQL 2005 SP1 and would like to upgrade it to SP2 but afraid to do so. Did anyone dared to do this successfully?

Thanks