So, My customer had a problem last time he rebooted his vCenter server. Once the server came back up. VMware VirtualCenter Server service did not start. A manual start of the service was also unsuccessful and the below error was reported:
I then asked my customer to check Windows event viewer logs and from there we found Event ID 1000 was reported in application event logs:
That was not really helpful so my next stop was at vpxd.log located at C:\ProgramData\VMware\VMware VirtualCenter\Logs. From the latest vpxd.log the below error was reported.
2014-04-10T03:13:45.682-07:00 [13324 info ‘ProxySvc’] Max proxy connections currently set to 0 (unlimited), buffer size: 16344 bytes 2014-04-10T03:13:45.682-07:00 [13324 info ‘ProxySvc’] vmacore/ssl/useSSLCtxPool: true 2014-04-10T03:13:45.698-07:00 [13324 info ‘ProxySvc’] vmacore/ssl/serializeServerHandshake: false 2014-04-10T03:13:45.698-07:00 [13324 error ‘vpxdvpxdMoReverseProxy’] [VpxdReverseProxy] Failed to create http proxy: An attempt was made to access a socket in a way forbidden by its access permissions.
Now, it was the time for VMware KB so I searched the knowledgebase articles from VMware and the most relevant one was KB1003926
Step 2 in the resolution was a bit interesting. I opened CMD and ran netstat command and the output was:
ouch, There was a service listening to port 80.
I checked tasklist output for PID 4 and the output was:
Further checks showed that one of the server admins accidentally installed IIS service and that was the one causing this issue.
I shutdown the World Wide Web Publishing Service and after that I was successfully able to start VMware VirtualCenter Server service