VMware service - will not start

[afr1]

Hello!

I have tried to install VC 2.0 about 10 times now and am quite frustrated. Everytime it looks OK but I am never able to get the VMware server service to start. I only get the message "The VMware VirtualCenter server on local computer started and then stopped. ....... "

What is wrong?

I have tried everything that people have mentioned earlier in discussion groups. I have also followed the installation description from VMware right to the point and have been running through a installation with my colleagues to dobbelt check my moves.

Please help me - I am going insane .....

[jonhutchings]

What database are you using for VC - is this all working and configured correctly ?

[Mazzer]

I'm with same problem,

I Instaled VC2, in Windows 2003 STD machine,

\- Client Oracle

\- ODBC Oracle

I'm using Oracle 9.2 (supported)

When service try to start i receive this log, in C:\temp\vpx

Log for VMware VirtualCenter, pid=2448, version=2.0.0, build=build-27704, option=Release, section=2

\[2006-09-26 16:28:43.222 'App' 2456 info] Current working directory:

C:\WINDOWS\system32

\[2006-09-26 16:28:43.222 'App' 2456 info] Initializing SSL context

\[2006-09-26 16:28:44.739 'BaseLibs' 2456 info] NFC connection accept

timeout: 180000 milliseconds

\[2006-09-26 16:28:44.739 'BaseLibs' 2456 info] NFC request timeout: 180000 milliseconds

\[2006-09-26 16:28:44.739 'BaseLibs' 2456 info] NFC read timeout: 60000 milliseconds

\[2006-09-26 16:28:44.739 'BaseLibs' 2456 info] NFC write timeout: 600000 milliseconds

\[2006-09-26 16:28:44.739 'App' 2456 info] Starting VMware VirtualCenter 2.0.0 build-27704

\[2006-09-26 16:28:44.739 'App' 2456 info] Account name: SYSTEM

\[2006-09-26 16:28:44.739 'App' 2456 info] \[VpxOsLayer] Enabled low-frag process heap.

\[2006-09-26 16:28:44.739 'App' 2456 info] \[VpxOsLayer] Enabled low-frag crt heap.

\[2006-09-26 16:28:44.739 'App' 2456 info] \[VpxLRO] 32 total threads

\[2006-09-26 16:28:44.739 'App' 2456 info] \[VpxLRO] 6 reserved internal threads

\[2006-09-26 16:28:44.739 'App' 2456 info] \[VpxLRO] 6 reserved blocker threads

\[2006-09-26 16:28:44.739 'App' 2456 info] \[VpxLRO] 6 reserved short threads

\[2006-09-26 16:28:44.739 'App' 2456 info] \[VpxLRO] 2 reserved long threads

\[2006-09-26 16:28:44.739 'App' 2456 info] \[VpxLRO] 600-second task lifetime

\[2006-09-26 16:28:46.396 'App' 2456 error] ODBC error: (HYC00) - \[Microsoft]\[ODBC driver for Oracle]Driver not capable

\[2006-09-26 16:28:46.411 'App' 2456 error] Failed to intialize VMware VirtualCenter. Shutting down...

\[2006-09-26 16:28:46.411 'App' 2456 info] Shutting down VMware VirtualCenter now

\----

---

Someone resolve this problem ?

[Jwoods]

When you installed the oracle client, did you perform a Admin install, custom install or the runtime install?

[bigusdadius]

What errors are you receiving in the Event Logs?

[KPA]

afr,

Try changing the ODBC Connection Type from NAMED PIPES to TCP/IP and restart the service.

This worked for me.

\- KPA

[Mazzer]

Hi Jwoods,

I solve the problem,

I used a runtime install, and this runtime don't install ODBC from Oracle. So i was using Microsoft ODBC Driver for Oracle. Now a chose custon install, select a bundle pakages who has ODBC from Oracle. And make a new ODBC conection in my server with this ODBC. And now works fine.

Thanks.

[AustinPowers]

I'm having exact same problem. Service starts then stops. I'm using SQL, connection type is TCP/IP. Log file shows

2006-09-29 16:34:41.656 'App' 3400 error] "ODBC error: (42S02) - \[Microsoft]\[ODBC SQL Server Driver]\[SQL Server]Invalid object name 'vpx_sequence'." is returned when executing SQL statement "select id from vpx_sequence where name = ?"

Help.

[Maurice_Perreij]

I have about the same problem as AustinPowers here.

The error message is:

\[2007-01-30 10:13:06.593 'App' 2512 error] "ODBC error: (42000) - \[Microsoft]\[ODBC SQL Server Driver]\[SQL Server]SELECT permission denied on object 'VPX_SEQUENCE', database 'master', owner 'dbo'." is returned when executing SQL statement "select id from vpx_sequence where name = ?"

[davidbarclay]

Running SQL 2005?

Check these instructions carefully

http://kb.vmware.com/vmtnkb/search.do?cmd=displayKC&docType=kc&externalId=6565318&sliceId=SAL_Public

Dave

[Maurice_Perreij]

No I am running SQL 2000 on a Windows 2003 SP1 server.

[blakethornton]

I'm seeing the same issue... or very nearly so.

Has anyone come up with a resolution?

\[2007-04-10 15:52:05.437 'App' 3204 error] An unrecoverable problem has occurred, stopping the VMware VirtualCenter service. Check database connectivity before restarting. Error: Error\[VdbODBCError] (-1) "ODBC error: (08S01) - \[Microsoft]\[ODBC SQL Server Driver]Communication link failure" is returned when executing SQL statement [b]"update vpx_sequence set id = ? where name = ?"[/b][/i]

\[2007-04-10 15:52:05.437 'App' 3204 info] Shutting down VMware VirtualCenter now

[egray]

This seems like a different problem. I suspect you are seeing this because your database has been restarted or rebooted. If that happens, VC needs to shut down and restart to establish new connections to the DB.

As of VC 2.0.1 patch 2, you can use the service control manager recovery options to have the VC service be restarted automatically when this happens. By default it is configured to restart on the first failure.

[nonu]

We also faced above stated error i.e.

"ODBC error: (42S02) - \[Microsoft]\[ODBC SQL Server Driver]\[SQL Server]Invalid object name 'vpx_sequence'." is returned when executing SQL statement "select id from vpx_sequence where name = ?"

We have VC 2.0.1 and SQL 2005 SP2.. but in our case.. problem was on the database side.. the transaction log had grown too it's maximum size and wasn't able to complete the authentication, as SQl won't allow VC to write in the log due to the restriction on the size of the log..

So old log file was dumped and new was created which would allowed VC to write in the transaction log,also the size restriction was removed.

Message was edited by:

nonu

[Rangey]

Just to add my 2 cents worth , I had the same problem, vmware virtualcenter service wouldnt start, it turned out to be that the ODBC user account did not have high enough rights to the SQL DB, once this had been changed to DB owner, everything was able to function again