virtual centre service not starting

[harishms007]

Hi,

Im trying to start the VC server service and it is not starting in automatic or in manual mode. VC 2.5 ; SQL 2005 is installed locally. it is set to local system account. I tried even in connecting thru a seperate account configured for SQL and same error even though ODBC connection shows as test completed successfully.

The VMware VirtualCenter Server service terminated with service-specific error 2 (0x2)

Log looks like below, Any advice.

Log for VMware VirtualCenter, pid=1956, version=2.5.0, build=build-64192, option=Release, section=2

Current working directory: C:\WINDOWS\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-64192

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

Invoking callbacks for key vpxd.npivWwnGeneration.singleNodeWwn

Invoking callbacks for key vpxd.npivWwnGeneration.portWwnNumber

Locale subsystem initialized from E:\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-160) nic:GuestInfo.net[0].ipAddress[0] and entity (moId:vm-148)

Local Domain : GROUPINFRA

IsWorkgroup: No

Local Machine: UK-AP040

Default resource used for 'LicenseRestrictedEvent.category' expected in module 'event'.

Default resource used for 'LicenseRestrictedEvent.fullFormat' expected in module 'event'.

Default resource used for 'LicenseRestrictedEvent.formatOnDatacenter' expected in module 'event'.

Default resource used for 'LicenseRestrictedEvent.formatOnComputeResource' expected in module 'event'.

Default resource used for 'LicenseRestrictedEvent.formatOnHost' expected in module 'event'.

Default resource used for 'LicenseRestrictedEvent.formatOnVm' expected in module 'event'.

Failed to create http proxy: Resource is already in use: Listen socket: :80

Failed to intialize VMware VirtualCenter. Shutting down...

Forcing shutdown of VMware VirtualCenter now

[jparnell · Accepted solution]

"Failed to create http proxy: Resource is already in use: Listen socket: :80"

Do you already have something listening on port 80? maybe IIS or Apache?

If you run #netstat -abn, what do you see listening on port 80? It looks like this port is already in use, and VC is failing to start because of this.

[wpatton]

During the installation of VC Server, you also do have the option to change the port it uses to something other than 80. If you are running IIS or Apache on the system already, it might be as simple as changing the port to 81.

If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".

[Cameron2007]

change the port to 8080 for example. Also check when you setup the databse that you called it VCDB. Even though the default on the installation GUI says "Virtual Center Server" it will now work for strings longer than 10 characters or that have white space hence VCDB.

[msinko]

Just uninstall the IIS, it can not cohabitate with VC.

[wpatton]

It most certainly can cohabitate, VMWare has even posted documents on using VC 1.x with IIS. Using them seperately for different functions just requires changing the port of one of them from 80 to another port of your choosing, just the same change is required if running Apache and IIS on the same where, which is common.

If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".

[msinko]

You're exactly right, it's just common practice to at least disable iis service.