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

Skip to main content

My Subscriptions

Loading

Knowledge Base

Troubleshooting vpxd service on Windows vCenter Server (1003926)

Last Updated: 4/8/2021Categories: TroubleshootingTotal Views: 42515Language:
Chinese (Simplified)KoreanJapaneseSpanishEnglish

18 like this article

Subscribe to get an email
newsletter with new updates

18 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Symptoms

vmware-vpxd service failed to start.

You cannot connect to VMware vCenter Server with the vSphere Client.

You cannot see the VMware vCenter Server in the inventory in the vSphere Web Client.

You may see a 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_name: No connection could be made because the target machine actively refused it.

Attempting to start the VMware VirtualCenter Server service fails.

You may 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 C:\ProgramData\VMware\VMware VirtualCenter\Logs\vpxd.log file on vCenter Server, you may 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></time> 02128 error 'App'] [Vpxd::ServerApp::Init] Init failed: VpxdMoReverseProxy::Init()
<YYYY-MM-DD>T<time></time> 02128 warning 'VpxProfiler'] ServerApp::Init took 29328 ms
<YYYY-MM-DD>T<time></time> 02128 error 'App'] Failed to intialize VMware VirtualCenter. Shutting down...
<YYYY-MM-DD>T<time></time> 02128 info 'App'] Forcing shutdown of VMware VirtualCenter now</time>

Purpose

This article provides steps to troubleshoot a vCenter Server service which does not start or has failed.

Cause

Potential causes of vpxd service failing on vCenter Server for Windows include, but not limited to:

Inability to connect to the vCenter Server database, especially when it is on an external server

Other database problems, such as bad or corrupt information in tables or in the ODBC configuration file

Corruption of critical .dlls or configuration files in the Windows system

Disk problems on the vCenter or external database server

Incompatible plug-ins

Missing critical vCenter Server files or folders

Incompatible hardware changes to the vCenter Server machine

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 Virtual Center 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.

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.

For vCenter Server 6.x, see How to Stop, Start or Restart vCenter Server 6.x Services.

For version 6.0 only, verify the inventory service is able to start in vCenter Server.

Resetting the VMware vCenter Server 6.0 Inventory Service's Individual Data Providers

Note: The Inventory service is no longer a separate service in versions 6.5/6.7.

Verify that the connection to the vCenter database is correct and working.

Check the ODBC Data Source Name (DSN) used for connection to the database for vCenter Server is correct. For more information, see: ODBC and DSN errors installing vCenter Server

Check whether the database server machine is running, or the database application is down.

If not, your database administrator may need to get it working

Check whether the database user password has changed. See Changing the vCenter Server database user ID and password

If not, your database administrator might have to provide the correct password or change it

Verify that DNS or Active Directory contains the correct IP information for both the vCenter Server machine and the database server if that server is separate from the vCenter machine.

If not, your DNS/AD team may have to correct the addresses

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.

Verify that the required ports are available on the vCenter Server machine. For more information, see TCP and UDP Ports required to access VMware vCenter Server, VMware ESXi and ESX hosts, and other network components. 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 VMware vCenter Server.

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_number

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_number: 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.

Verify the firewall is allowing the ports.

Defaults are:

53 for DNS

80 for external SQL servers

88 and 135 for Active Directory

If your Windows internal firewall is preventing the traffic:

You may need to get your Windows Management team to change the settings

If an external network firewall is preventing the traffic:

You may need to get your network team to change the settings

See the VMware Ports and Protocols page for further information

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 troubleshooting steps when using a Microsoft SQL database, see Investigating the health of a vCenter Server database.

Verify whether the problem is due to vCenter Server database errors.

Navigate to the C:\ProgramData\VMware\vCenter Server\Logs\vmware-vpx directory

If your vCenter Server was installed to a different drive or directory, you'll need to look in that path

Open the most recent vpxd.log file in Notepad or other text editor.

Look for entries containing "error vpxd" and "SQL"

If found, there are likely to be database problems preventing vpxd from starting

Many database errors are best resolved by VMware technical staff. See How to file a Support Request in Customer Connect.

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.

Confirm that any plug-ins that are installed are compatible with your version of vCenter Server. Check with documentation to verify all installed plugins are compatible with the installed vCenter Server version. For more information, see Cannot remove or disable unwanted plug-ins from vCenter Server and vCenter Server Appliance.

Verify that critical folders exist on vCenter Server. For more information, see Missing folders on a vCenter Server prevent VirtualCenter Server service from starting.

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.

Please be aware sometimes an update will change configuration and removing it will not reverse the change

Updates will commonly re-activate a program such as Microsoft IIS that takes over a port required by vCenter Server. Check the list of services for such applications.

Look in the Windows System and Application event logs for any information showing there is a problem with a vCenter Server .dll file

If so, vCenter Server will likely need to be restored from backup or reinstalled.

Before launching vCenter Server 5.x, ensure that the VMwareVCMSDS service is running. For more information, see Installing VMware vCenter Server 5.0 fails with the error: Error 28023. Setup failed to setup VMwareVCMSDS directory service instance.

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.

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

Gather the VMware Support Script Data. For more information, see Collecting diagnostic information for VMware products (1008524).

File a support request with VMware Support and note this Knowledge Base article ID (1003926) in the problem description. For more information, see How to Submit a Support Request.

Related 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.

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.

For information on troubleshooting vpxd service problems in the vCenter Server Appliance, see:
vpxd service fails to start

For different language, see:
vCenter Server 上で VMware VirtualCenter Server サービスが起動しない、あるいは失敗する場合のトラブルシューティング
Solucionar problemas del servicio de VMware VirtualCenter Server cuando este no se inicia o falla en el vCenter Server
排除 VMware VirtualCenter Server 服务在 vCenter Server 上未启动或失败时的故障

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)KoreanJapaneseSpanishEnglish

Attachments

Additional Resources

No results for undefined

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 6.7.x

VMware vCenter Server 6.5.x

VMware vCenter Server 6.0.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant