Search the VMware Knowledge Base (KB)
View by Article ID

After installing vCenter Server, the VMware VirtualCenter Server service fails to start (1004280)

  • 14 Ratings

Symptoms

  • After installing vCenter Server, the VirtualCenter Server service fails to start
  • Trying to start the VMware VirtualCenter Server service manually is not successful
  • Attempting to start VMware VirtualCenter Server, you may see the 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.
    • Virtual Center service specific error 2.
  • It is possible to start the service from the command-line. 
  • The vpxd.log (located at %ALLUSERSPROFILE%\Application Data\VMware\VirtualCenter\logs) contains the error:
Locale subsystem initialized from 
C:\Program Files\VMware\Infrastructure\VirtualCenter Server\locale/ with default locale en.
Locale '' not supported in module 'iso2win'.
Invalid server locale specified.
[VpxdMain] Failed to initialize: Invalid Locale.
Failed to initialize VMware VirtualCenter. Shutting down...
Forcing shutdown of VMware VirtualCenter now


Resolution

There are multiple reasons this issue can occur.  In order to resolve this, follow the steps below:
 
  1. Ensure that the system you use for your vCenter Server installation belongs to a domain rather than a workgroup. For more information, see VirtualCenter Server Prerequisites in the ESX Server 3 Installation Guide  or vSphere 4 vCenter Server Prerequisites in the ESX and vCenter Server Installation Guide.
  2. Ensure that the VirtualCenter Server service is using the right credentials. For example, if the credentials for the service belong to an account that only has Administrator privileges on a given domain, then the credentials must be changed to a domain account.

    To ensure vCenter Server is using the right credentials:

    1. Click Start > Run, type services.msc, and press Enter.
    2. Double-click VMware VirtualCenter Server Service.
    3. Click the Log On tab.
    4. Select This Account, type the name of the account in the format of DOMAINNAME\accountname , or click Browse and find the correct account.
    5. Enter the appropriate password for the account, in the Password and Verify Password fields.
    6. Click OK.
    7. Start the service.

  3. Ensure no services use the vCenter Server ports. The default for VirtualCenter WebAccess is port 80. Stop any services that may be using this port. For more information, see Configuring Communication Between VirtualCenter Components in the ESX Server 3 Installation Guide and Required Ports in the vSphere 4 ESX and vCenter Server Installation Guide.

Additional Information

For more information on troubleshooting why the VMware VirtualCenter Server service may not start, see Troubleshooting the VMware VirtualCenter Server service when it does not start or fails on vCenter Server (1003926).
 
For our complete list of documentation on Virtual Infrastructure, see https://www.vmware.com/support/product-support/vi3.html.

 

Tags

install-upgrade-vcenter-fails-error  install-vcenter-fails  install-vcenter-fails-error  vcenter-services

See Also

Update History

04/01/2011 - Updated to reflect 4.x.

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

  • 14 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)




Please enter the Captcha code before clicking Submit.
  • 14 Ratings
Actions
KB: