vCenter Service won’t start/Failed to create http proxy
I recently had a customer who’s vCenter service would not start on their management server. The Event 1000 error showed: “Failed to intialize VMware VirtualCenter. Shutting down…” Not very helpful!
Next, I checked the vpxd log files: %ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter\Logs\. In there I noticed the following error: [VpxdReverseProxy] Failed to create http proxy: An attempt was made to access a socket in a way forbidden by its access permissions. This indicated that something was using one of the vCenter ports (By default 80,443,902).
The next step for this was to find out what was using one of those ports. For that, we use the netstat command: netstat -bano > C:\netstat.txt (I will generally output this to text file as it makes it easier to search).
Search the output file for the ports VMware Ports listed above (or the non-standard ports you may have configured).
To check what application is related to the PID, open Task Manager and add PID to the view (View, Select Columns)
At this stage I had a pretty good idea what was using it. Jumped into IIS and sure enough, somebody had started the Default Website running on Port 80. Stopped the website and restarted the vCenter Service with no further issues