Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

The VMware VirtualCenter Server service fails to start with an Error code 2 (1017390)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 82677Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The VMware VirtualCenter Server service fails to start.

The Event Viewer shows the error:

Windows could not start VMware Virtual Center Service. Error code 2

The vpxd logs show errors similar to:

2010-01-18 10:06:42.418 03428 info 'App'] [Vpxd::ServerApp::Init:760] Calling: VpxdLdap::Init()
[2010-01-18 10:06:42.434 03428 info 'App'] [LdapBackup] Making sure LDAP instance VMwareVCMSDS is running
[2010-01-18 10:06:42.434 03428 info 'App'] [LdapBackup] Attempting to start service ADAM_VMwareVCMSDS...
[2010-01-18 10:06:42.434 03428 info 'App'] [LdapBackup] Service started
[2010-01-18 10:06:54.434 03428 error 'App'] [LDAP Client] Failed to connect to LDAP: 0x52 (Local error occurred.)
[2010-01-18 10:06:54.434 03428 error 'App'] [VpxdLdap] Failed to authenticate to LDAP. There is a misconfiguration of the LDAP server ("LDAP error 0x52: Local error occurred."). This may be due to invalid credentials, or to a problem with connectivity to a domain controller, if this machine belongs to a domain and VMware VirtualCenter is running as the LocalSystem account.
[2010-01-18 10:06:54.434 03428 error 'App'] [Vpxd::ServerApp::Init] Init failed: VpxdLdap::Init()
[2010-01-18 10:06:54.434 03428 error 'App'] Failed to intialize VMware VirtualCenter. Shutting down...
[2010-01-18 10:06:54.434 03428 info 'App'] Forcing shutdown of VMware VirtualCenter now

Resolution

This issue occurs when vCenter Server is installed on a machine that is part of an Active Directory domain, but while the VirtualCenter Server service is being started, the domain relationship is not working. The domain relationship may not be working because the domain controller is down, because of a network connectivity issue, or because the domain relationship for the machine is not valid anymore.

If the machine on which vCenter Server is installed is part of an Active Directory domain, the relationship must be healthy.

To resolve this issue:

Verify that the vCenter Server can resolve the FQDN of the Active Directory server using the nslookup command in a Windows command prompt.

Ensure that the Active Directory server is running and accessible from the vCenter Server machine.

If you are aware of a specific issue with your Active Directory server / services, and those are being worked on by another organizational unit as a temporary workaround you can adjust the logon settings in the VMware VirtualCenter service properties not to use the Local system account and configure it to use another account for example, specify the username as Administrator and provide the appropriate password.

Start the VMware VirtualCenter service first, then start the VMware Management Webservices (you can leave the logon settings for the Management Webservices service as Local system account, as this is just a temporary workaround). Remember that any vCenter functions that normally rely on the Active Directory to work, will still fail, but you will be able to perform activities that are not dependent on the Active Directory such as vMotion.

Related Information

In addition ensure that you check all network connections, and that the username and password that is connected to your vCenter Server database is correct. Network connection issues, and user account authentication problems can cause the above symptoms as well.エラー コード 2 で VMware VirtualCenter Server サービスの起動に失敗する
VMware VirtualCenter Server 服务启动失败，并显示错误代码 2

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
完了まで時間のかかる VMware tools のパワーオフやサスペンド用カスタムスクリプトを実行すると、次のエラーで失敗する：A general system error occurred: Invalid Fault (2088472)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server 4.0.x

Take Our Survey

Support Assistant