VMware Cloud Community

URGENT Help!! VC service is not starting

http://Sorry to use the word URGENT in subject. It is really urgent infact

I restarted my VC server after windows patch updates and the Virtual Center service is not starting after that. My server is running with VC 2.5 Update 2

I am getting the below error while starting the service.




Windows could not start the VMware VirtualCenter Server on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 2.




And VC log is givign errors about port and manged IP. I don't have any other services using the port that VC use. Please help me in resolving this issue



Log for VMware VirtualCenter, pid=1568, version=2.5.0, build=build-84767, option=Release, section=2

Current working directory: C:\WINNT\system32

HOSTINFO: Seeing Intel CPU, numCoresPerCPU 2 numThreadsPerCore 1.

HOSTINFO: This machine has 1 physical CPUS, 2 total cores, and 2 logical CPUs.

Log path: C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\Logs

Initializing SSL

Using system libcrypto, version 90709F

Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 120000000

Starting VMware VirtualCenter 2.5.0 build-84767

Log directory: C:\Documents and Settings\Default User\Local Settings\Application Data\VMware\vpx.

Account name: SYSTEM

Enabled low-frag process heap.

Enabled low-frag crt heap.

34 max LROs

6 reserved internal LROs

6 reserved blocker LROs

6 reserved short LROs

4 reserved long LROs

600-second task lifetime

Couldn't read registry entry vmdbPort

Couldn't read registry entry managedIP

Ignoring unknown entry from DB: AgentUpgrade.maxConcurrentUpgrades

Ignoring unknown entry from DB: Perf.Stats.FilterLevel

Invoking callbacks for key vpxd.npivWwnGeneration.singleNodeWwn

Invoking callbacks for key vpxd.npivWwnGeneration.portWwnNumber

Locale subsystem initialized from C:\Program Files\VMware\Infrastructure\VirtualCenter Server\locale/ with default locale en.

Initializing SSL Contexts

Setting VerifySSLCertificates to FALSE

detected IP conflict between vm (moId:vm-1199) nic:GuestInfo.net[0].ipAddress[0] and entity (moId:vm-199)

Failed to initialize: not well-formed (invalid token)

Failed to intialize VMware VirtualCenter. Shutting down...

Forcing shutdown of VMware VirtualCenter now


0 Kudos
1 Reply

First I would run a registry check / fix on your server. While that's working, I would verify that your ODBC connections to your DB instance are working. Normally VC balks at starting if it can't reach the DB, but this looks like you have some program errors.

If all else fails, reinstall VC and use ALL the same information previously (and don't initialize the DB). VC is really easy to fix, but fix the registry ASAP.

0 Kudos