Re: vCenter Server Service is not starting

Please try these things...

To troubleshoot the VMware VirtualCenter Server service when it does not start or fails:

Note: If you perform a corrective action in any of the following 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 VirtualCenter service if it has stopped, see Stopping, starting, or restarting vCenter services (1003895).
   

2. Verify that the configuration of the ODBC Data Source (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 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 4.x and above Windows Authentication is supported.
   
   

3. Verify that ports 902, 80, 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) or Routing and Remote Access Service (RAS) or the World Wide Web Publishing Services (W3SVC) or Windows Remote Management service (WS-Management) or the Citrix Licensing Support service is utilizing any of the ports, vCenter Server cannot start. For more information, seePort already in use when installing vCenter Server (4824652).

   
   If you see an error similar to one of the following 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).
     
     

4. 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).
   
   

5. Verify the VMware VirtualCenter Service is running with the proper credentials. For more information, see After installing vCenter Server, the VMware VirtualCenter Server service fails to start (1004280).
   
   

6. Verify that critical folders exist on the vCenter Server host. For more information, see Missing folders on a vCenter Server prevent VirtualCenter Server service from starting (1005882).
   
   

7. Verify that no hardware or software changes have been made to the vCenter server that may have caused the failure. If you have recently made any changes to the vCenter server, undo these changes temporarily for testing purposes.
   
   

8. Before launching vCenter Server, ensure that the VMwareVCMSDS service is running
   
   
   VMware Link :  http://kb.vmware.com/selfservice/documentLinkInt.do?micrositeID=&popup=true&languageId=&externalID=1003926