"Error waiting for service rhttpproxy start. Exit code: 1066" error when starting vCenter Server 6.0

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• vCenter Server 6.0 service fails to start with the error:
  
  Error waiting for service rhttpproxy start. Exit code: 1066

• When starting the services with the command service-control --start --all, you see errors similar to:
   
  INFO:root:Service: rhttpproxy, Action: start
  Service: rhttpproxy, Action: start

  YYYY-MM-DDT<time> State for service rhttpproxy: STOPPED</time>

  YYYY-MM-DDT<time> Error waiting for service rhttpproxy start. Exit code: 1066 Current State: 1</time>

  ERROR:root:Unable to start service rhttpproxy, Exception: {

  "resolution": null,

  "detail": [

  {

  "args": [

  "rhttpproxy"

  ],

  "id": "install.ciscommon.service.failstart",

  "localized": "An error occurred while starting service 'rhttpproxy'",

  "translatable": "An error occurred while starting service '%(0)s'"

  }

  ],

  "componentKey": null,

  "problemId": null

  }

  Unable to start service rhttpproxy, Exception: {

  "resolution": null,

  "detail": [

  {

  "args": [

  "rhttpproxy"

  ],

  "id": "install.ciscommon.service.failstart",

  "localized": "An error occurred while starting service 'rhttpproxy'",

  "translatable": "An error occurred while starting service '%(0)s'"

  }

  ],

  "componentKey": null,

  "problemId": null

  }

• In the %PROGRAMDATA%\VMware\vCenterServer\logs\rhttpproxy\rhttpproxy.log file, you see entries similar to:
   
  YYYY-MM-DDT<time> Section for VMware VirtualCenter, pid=2520, version=6.0.0, build=2656760, option=Release</time>

  YYYY-MM-DDT<time> verbose rhttpproxy[02460] [Originator@6876 sub=Default] Dumping early logs:</time>

  YYYY-MM-DDT<time> warning rhttpproxy[02460] [Originator@6876 sub=Default] Unrecognized log/level '' using 'info'</time>

  YYYY-MM-DDT<time> info rhttpproxy[02460] [Originator@6876 sub=Default] Logging uses fast path: true</time>

  YYYY-MM-DDT<time> info rhttpproxy[02460] [Originator@6876 sub=Default] The bora/lib logs WILL be handled by VmaCore</time>

  YYYY-MM-DDT<time> info rhttpproxy[02460] [Originator@6876 sub=Default] Initialized channel manager</time>

  YYYY-MM-DDT<time> info rhttpproxy[02460] [Originator@6876 sub=Default] Current working directory: C:\Windows\system32</time>

  YYYY-MM-DDT<time> info rhttpproxy[02460] [Originator@6876 sub=Default] ThreadPool windowsStackImmediateCommit = true</time>

  YYYY-MM-DDT<time> info rhttpproxy[02460] [Originator@6876 sub=ThreadPool] Thread pool on asio: Min Io, Max Io, Min Task, Max Task, Max Concurency: 2, 44, 2, 18, 2147483647</time>

  YYYY-MM-DDT<time> info rhttpproxy[02460] [Originator@6876 sub=ThreadPool] Thread enlisted</time>

  YYYY-MM-DDT<time> info rhttpproxy[04644] [Originator@6876 sub=ThreadPool] Thread enlisted</time>

  YYYY-MM-DDT<time> info rhttpproxy[02460] [Originator@6876 sub=Default] Listening on HTTP port 80.</time>

  YYYY-MM-DDT<time> info rhttpproxy[01096] [Originator@6876 sub=ThreadPool] Thread enlisted</time>

  YYYY-MM-DDT<time> info rhttpproxy[05852] [Originator@6876 sub=ThreadPool] Thread enlisted</time>

  YYYY-MM-DDT<time> info rhttpproxy[04444] [Originator@6876 sub=ThreadPool] Thread enlisted</time>

  YYYY-MM-DDT<time> error rhttpproxy[02460] [Originator@6876 sub=Default] Application error: An attempt was made to access a socket in a way forbidden by its access permissions</time>

  YYYY-MM-DDT<time> error rhttpproxy[02460] [Originator@6876 sub=Default] Backtrace:</time>

  -->

  --> [backtrace begin] product: VMware VirtualCenter, version: 6.0.0, build: build-2656760, tag: rhttpproxy

  --> backtrace[00] vmacore.dll[0x001BC4DA]

  --> backtrace[01] vmacore.dll[0x0005B99F]

  --> backtrace[02] vmacore.dll[0x0005CACE]

  --> backtrace[03] vmacore.dll[0x00012C3B]

  --> backtrace[04] vmacore.dll[0x001BBA05]

  --> backtrace[05] vmacore.dll[0x00165FEB]

  --> backtrace[06] vmacore.dll[0x0016608A]

  --> backtrace[07] vmacore.dll[0x003398A9]

  --> backtrace[08] MSVCR90.dll[0x00074830]

  --> backtrace[09] MSVCR90.dll[0x00043B3C]

  --> backtrace[10] ntdll.dll[0x00093583]

  --> backtrace[11] vmacore.dll[0x00172F69]

  --> backtrace[12] vmacore.dll[0x0017FA9C]

  --> backtrace[13] rhttpproxy.exe[0x00002B6F]

  --> backtrace[14] rhttpproxy.exe[0x00003A08]

  --> backtrace[15] rhttpproxy.exe[0x000017B3]

  --> backtrace[16] sechost.dll[0x00005ADA]

  --> backtrace[17] KERNEL32.DLL[0x000013D2]

  --> backtrace[18] ntdll.dll[0x00015454]

  --> [backtrace end]
   

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware vCenter Server 6.5.x
VMware vCenter Server 6.7.x
VMware vCenter Server 6.0.x

Cause

This issue occurs when another service running on vCenter Server is using port 80.

 

 

Resolution

1. Determine the service which is using port 80.
   1. Open a Windows Command Prompt as Administrator, and run this command:
      netstat -bano | findstr 80
      Note the Process ID (PID) of the service listening on port 80.
      For example:
      TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 1120
      where 1120 is the PID of the service listening on port 80.
   2. To determine the service corresponding to the PID found in Step 1b, run the command:
      C:\>tasklist /svc | findstr 1120
      You see an output similar to:
      webservice.exe 1120
      where webservice.exe is the service which is having Process ID as 1120.
2. Stop or uninstall the service identified in Step 1b.
3. Start all the vCenter Server services from installation_directory\Program Files\VMware\vCenter Server\bin by running the command:
   service-control --start --all

Note: VMware recommends that vCenter Server must be installed on a dedicated server to avoid conflicts or instability of the vCenter Server service.