Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Troubleshooting the VMware VirtualCenter Server service when it does not start or fails on vCenter Server (1003926)

Symptoms

  • You cannot connect to VMware vCenter Server.
  • You see an Microsoft Windows Event error associated with IIS similar to:

    Event properties - Event 7024, Service Control Manager
    The VMware VirtualCenter Server service terminated with service-specific error The system cannot find the file specified..
    Log Name: System
    Source: Service Control
    Event ID: 7024
    Level: Error

    Note: A windows Event ID 1000 may also be reported in relation to this issue.

  • Connecting to vCenter Server fails with the error:

    Cannot connect to host <server>: No connection could be made because the target machine actively refused it.

  • Attempting to start the VMware VirtualCenter Server service fails.
  • You see this error:

    Windows could not start the VMware VirtualCenter Server service on Local Computer. Error 2: The system cannot find the file specified.

  • If you try to start the VMware VirtualCenter Server service, you may see these errors:

    • Could not start the VMware VirtualCenter Server service on Local Computer. Error 1067: The process terminated unexpectedly.
    • Could not start the VMware VirtualCenter Server service on Local Computer. Error 1069: The service did not start due to a logon failure.
    • The VMware VirtualCenter Server Service on Local Computer started then stopped. Some services stop automatically if they have no work to do, for example the Performance Logs and Alerts service.

  • In the %ALLUSERSPROFILE%\VMware\VMware VirtualCenter\Logs\vpxd.log file on vCenter Server, you see entries similar to:

    • [VpxdReverseProxy] Failed to create http proxy: An attempt was made to access a socket in a way forbidden by its access permissions.
      [Vpxd::ServerApp::Init] Init failed: VpxdMoReverseProxy::Init()
      Failed to intialize VMware VirtualCenter. Shutting down...
      Forcing shutdown of VMware VirtualCenter now

    • <YYYY-MM-DD>T<TIME> 02128 error 'App'] [VpxdReverseProxy] Failed to create http proxy: An attempt was made to access a socket in a way forbidden by its access permissions.
      <YYYY-MM-DD>T<TIME> 02128 error 'App'] [Vpxd::ServerApp::Init] Init failed: VpxdMoReverseProxy::Init()
      <YYYY-MM-DD>T<TIME> 02128 warning 'VpxProfiler'] ServerApp::Init took 29328 ms
      <YYYY-MM-DD>T<TIME>7 02128 error 'App'] Failed to intialize VMware VirtualCenter. Shutting down...
      <YYYY-MM-DD>T<TIME> 02128 info 'App'] Forcing shutdown of VMware VirtualCenter now


      Note: In Windows 2008, the vpxd.log file is located at C:\ProgramData\VMware\VMware VirtualCenter\Logs.

Resolution

Notes:
  • Validate if each troubleshooting step below is true for your environment. Each step provides instructions or a link to a document that helps eliminate possible causes and take corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Do not skip a step.
  • Completing the prescribed steps in this section may help to eliminate common causes of this problem by verifying the database configuration, validating network connectivity, and verifying the configuration of the Vmware VirtualCenter Server service.
To troubleshoot the VMware VirtualCenter Server service when it does not start or fails:

Note: If you perform a corrective action in any of these steps, attempt to restart the VMware VirtualCenter Server service.
  1. Verify that the VMware VirtualCenter Server service cannot be restarted.

    Open the Microsoft Services control panel and check the status of the service. For more information on starting the VMware VirtualCenter service if it has stopped, see Stopping, starting, or restarting vCenter services (1003895).

  2. Verify that the configuration of the ODBC Data Source Name (DSN) used for connection to the database for vCenter Server is correct. For more information, see vCenter Server installation fails with ODBC and DSN errors (1003928).

    Note: For version vCenter Server 2.5.x, ensure that you are using SQL authentication. If you are using a Microsoft SQL server, Windows authentication is not supported. For version vCenter Server 4.x and later, Windows authentication is supported.

  3. Verify if there is enough free disk space on vCenter Server. For more information, see The VMware VirtualCenter Server service does not start due to insufficient disk space (2083927).
  4. Verify that ports 902, 80, 8080, 8433 and 443 are not being used by any other application. If another application, such as Microsoft Internet Information Server (IIS) (also known as Web Server (IIS) on Windows 2008 Enterprise), Routing and Remote Access Service (RAS), World Wide Web Publishing Services (W3SVC), Windows Remote Management service (WS-Management) or the Citrix Licensing Support service are using any of the ports, vCenter Server cannot start.

    For more information, see Port already in use when installing vCenter Server (4824652).

    If you see an error similar to one of these when reviewing the logs, another application may be using the ports:

    • Failed to create http proxy: Resource is already in use: Listen socket: :<port>
    • Failed to create http proxy: An attempt was made to access a socket in a way forbidden by its access permissions.
    • proxy failed on port <port>: Only one usage of each socket address (protocol/network address/port) is normally permitted.

      For more information on checking ports, see Determining if a port is in use (1003971).

  5. Verify the health of the database server that is being used for vCenter Server. If the hard drives are out of space, the database transaction logs are full, or if the database is heavily fragmented, vCenter Server may not start. For more information, see Investigating the health of a vCenter Server database (1003979).
  6. Verify if the VMware VirtualCenter Server service is running with the proper credentials. For more information, see After installing vCenter Server, the VMware VirtualCenter Server service fails to start (1004280).
  7. Verify that critical folders exist on vCenter Server. For more information, see Missing folders on a vCenter Server prevent VirtualCenter Server service from starting (1005882).
  8. Verify that no hardware or software changes are made to vCenter Server that causes the issue. If you have recently made any changes to the vCenter Server, undo these changes temporarily for testing purposes.
  9. Before launching vCenter Server, ensure that the VMwareVCMSDS service is running.
  10. Verify that the vpxd.exe file is present in C:\Program Files\VMware\Infrastructure\VirtualCenter Server\vpxd.exe location. If this file is not present, reinstall vCenter Server.

Notes: If your problem still exists after trying the steps in this article:

Additional Information

Reviewing the vpxd log files is another common method of diagnosing vCenter Server when it does not start. By reviewing the log files, you can quickly determine the cause of the problem based on the error message reported. 
  • For vCenter Server 4.x, the log files are stored in this directory by default:

    %ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter\Logs
     
    For example:
     
    C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\Logs

     
  • For vCenter Server 2.5.x, the log files are stored in this directory by default:
     
    C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\Logs

  • For VirtualCenter Server 2.0.x, the log files are stored in this directory by default:
     
    C:\Windows\Temp\vpx
     
    To review the logs, open the most recent log in an editor, such as Notepad, and navigate to the bottom of the file. If there were any errors during the VirtualCenter Server startup service, it is listed in the file.

See Also

Update History

04/08/2011 - Updated for 4.1. 04/19/2010 - Added vCenter Server 4.0 to Products. 10/13/2011 - Additional additional log in Symptoms. 11/10/2011 - Added link to 1007669 in the See Also section 09/03/2012 - Added that the VMwareVCMSDS service needs to be running before launching vCenter Server 04/30/2013 - Added vCenter Server 5.1.x to Products 07/10/2013 - Added additional services impeding vCenter Server service from starting

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 107 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 107 Ratings
Actions
KB: