Unable to start virtualcenter service

[gh0stw4lk]

Our VirtualCenter won't start. The service starts , then immediately stops. The vxpd event log shows the following:

MOB started on port 8087

http proxy failed on port 8080: Only one usage of each socket address (protocol/network address/port) is normally permitted.

Failed to start http proxy: Only one usage of each socket address (protocol/network address/port) is normally permitted.

Shutting down VMware VirtualCenter...

Message file access using key 'enum.VirtualMachine.PowerState..label' with no default supplied.

Default resource used for 'VirtualMachine.PowerState..label' expected in module 'enum'.

Message file access using key 'enum.VirtualMachine.PowerState..label' with no default supplied.

Default resource used for 'VirtualMachine.PowerState..label' expected in module 'enum'.

Message file access using key 'enum.VirtualMachine.PowerState..label' with no default supplied.

Default resource used for 'VirtualMachine.PowerState..label' expected in module 'enum'.

Message file access using key 'enum.VirtualMachine.PowerState..label' with no default supplied.

Default resource used for 'VirtualMachine.PowerState..label' expected in module 'enum'.

Message file access using key 'enum.VirtualMachine.PowerState..label' with no default supplied.

Default resource used for 'VirtualMachine.PowerState..label' expected in module 'enum'.

Message file access using key 'enum.VirtualMachine.PowerState..label' with no default supplied.

Default resource used for 'VirtualMachine.PowerState..label' expected in module 'enum'.

Message file access using key 'enum.VirtualMachine.PowerState..label' with no default supplied.

Default resource used for 'VirtualMachine.PowerState..label' expected in module 'enum'.

Message file access using key 'enum.VirtualMachine.PowerState..label' with no default supplied.

Default resource used for 'VirtualMachine.PowerState..label' expected in module 'enum'.

Message file access using key 'enum.VirtualMachine.PowerState..label' with no default supplied.

Default resource used for 'VirtualMachine.PowerState..label' expected in module 'enum'.

Message file access using key 'enum.VirtualMachine.PowerState..label' with no default supplied.

Default resource used for 'VirtualMachine.PowerState..label' expected in module 'enum'.

Win32SEHTranslator: Access Violation (0xc0000005) ebp: 0x358f870, eip: 0x709838

Exception: Assert failed!

Backtrace:

(backtraces not supported)

CoreDump: Writing minidump to C:\Documents and Settings\Default User\Application Data\VMware\vpxd-4836-7268.dmp

Vmdb_Set: Failed to set /state/ to allocated (Schema path not found)

The executable that starts listening on port 8080 is tomcat.exe, which I believe is part of the virtualcenter install, so I'm not sure why the multiple socket error occurs.

A reboot of the virtualcenter server does not assist.

This problem seems to closely relate to an SQL patch installed on the remote SQL server, yet the ODBC connection from the VC server advises that it connects to the DB fine.

VC version is 2.0.1

If anyone could assist that would be greatly appreciated.

Dan

[rgv75]

Check on the VC Server's HKLM/Software/VMWare, Inc,/VMware VirtualCenter/DB, string #2, to see if you're still using a SQL Server account for authentication. Connection to the database by the VC uses the account in the registry for authentication, not the one used on the DSN. If using a domain account, make sure to use a SQL server account. If you need to change the account, change the account in the registry, then run "vpxd.exe" with the "-p" (vpxd -p) to change the password stored in the registry. From here, try restarting the service again. Good luck.

[gh0stw4lk]

Thanks for the tip, but that does not seem to be the problem. The registry has the correct account, and I've reset the password to make sure, but the same problem is still occuring

[mike_laspina · Accepted solution]

Hello,

You need to check what application/service is using port 8080 while the VC is stopped.

open a cmd window and issue

netstat -b -a

if its a service search the reg for that exe if it show up in the services area then disable and stop the named offensive service.

[gh0stw4lk]

Thanks Mike, I had already done that and found that tomcat.exe was listening on that port. I made the stupid assumption that tomcat was doing this on behalf of VC! After stopping tomcat, all works OK. Now to find out who installed the application that installed tomcat :smileymischief:

Thanks for the prompt.

Dan

[mike_laspina]

Your Welcome,

Yes, Seeing tomcat running would be missleading since VC does use it.

n.b. Awarding points is great way to say thanks in the forum.