Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

"An error occurred while starting service rhttpproxy" upgrading vCenter Server 6.0 U2 to 6.0 U3 (52215)

Last Updated: 8/16/2019Categories: TroubleshootingTotal Views: 9449Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

You see the error: An error occurred while starting service rhttpproxy

Updating vCenter Server 6.0 U2 to 6.0 U3b fails with below error %TEMP%\vminst.log file

"Installation of component VMware vCenter Server failed with error code '3010'. Check the logs for more details."

In the %TEMP%\vminst.log file, you see entries similar to: 2017-08-23 16:32:52.787+02:00| vcsInstUtil-5318198| I: wWinMain: Exe is told to run "Z:\vCenter-Server\Packages\vmware-vpxd.msi" with "ALLUSERS=1 ARPSYSTEMCOMPONENT=1 INSTALLPATH="C:\VMware\vCenter Server\" APPDATAPATH="C:\ProgramData\VMware\vCenterServer\"  REINSTALLMODE=vemus VM_UPDATE=1" details 0 2017-08-23 16:33:55.908+02:00| vcsInstUtil-5318198| E: wWinMain: MSI result of install of "Z:\vCenter-Server\Packages\vmware-vpxd.msi" may have failed: 3010 (0x00000bc2) 2017-08-23 16:33:55.908+02:00| vcsInstUtil-5318198| E: LaunchPkgMgr: Operation on vmware-vpxd.msi appears to have failed: 3010 (0x00000bc2) 2017-08-23 16:33:55.908+02:00| vcsInstUtil-5318198| I: PitCA_MessageBox: Displaying message: "Installation of component VMware vCenter Server failed with error code '3010'. Check the logs for more details."

Installation of the VMware vCenter server fails with 1603 error during an update from 6.0 U2 to 6.0 U3. In the run-updateboot-scripts.log file, you see entries similar to:

2019-05-31T13:14:56.619Z   State for service rhttpproxy: STOPPED
Unable to start service rhttpproxy, Exception: {^M^M
"resolution": null,
"detail":
{
"args": [
"rhttpproxy"
],
"id": "install.ciscommon.service.failstart",
"localized": "An error occurred while starting service 'rhttpproxy'",
"translatable": "An error occurred while starting service '%(0)s'"
}
],
"componentKey": null,
"problemId": null

Log file location %ProgramData%\VMware\CIS\logs\firstboot\

run-updateboot-scripts.log

2019-06-14 07:39:00.309-07:00| vcsInstUtil-13638470| I: UpdatePackageList: Disabling installation of package C:\Users\vmware\Downloads\VMware-VIMSetup-all-6.0.0-13638623\vCenter-Server\Packages\vmware-python.msi (ProductCode is different but ProductVersion is smaller than the one already on the system)

%TEMP%\vminst.log
2019-06-14 08:20:43.734-07:00| vcsInstUtil-13638470| E: wWinMain: MSI result of install of "C:\Users\vmware\Downloads\VMware-VIMSetup-all-6.0.0-13638623\vCenter-Server\Packages\vcsservicemanager.msi" may have failed: 1603 (0x00000643)
2019-06-14 08:20:43.734-07:00| vcsInstUtil-13638470| E: LaunchPkgMgr: Operation on vcsservicemanager.msi appears to have failed: 1603 (0x00000643)
2019-06-14 08:20:43.736-07:00| vcsInstUtil-13638470| I: PitCA_MessageBox: Displaying message: "Installation of component VCSServiceManager failed with error code '1603'. Check the logs for more details."

Cause

This issue occurs due to OpenSSL not updating during the upgrade due to bad/incorrect entries in the registry. The installer sees version (5.5) of OpenSSL is still installed causing the failure.

Resolution

This issue is resolved in vCenter Server 6.0 U3g, available at VMware Patch Downloads.

Workaround

To work around the An error occurred while starting service rhttpproxy issue, uninstall vmware-Openssl version 6.0.0.60000 and then try upgrading.

Note: Take a snapshot before proceeding.

Workaround 1:

Open the Command Prompt as Administrator

Run the below command

msiexec /x {7CA4FE96-7C9E-40ED-ABF7-3EA5D78529D3}

Re-run the Upgrade.

Workaround 2:

Type regedit in the edit field

Go to the below registry location

HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/CurrentVersion/Uninstall

Under this Uninstall folder you will find many registry entries

Click on Edit tab and then Find string "7CA4FE96-7C9E-40ED-ABF7-3EA5D78529D3"

Highlight the key and then Right click on it and choose Delete.

Related Information

"Error waiting for service rhttpproxy start. Exit code: 1066" error when starting vCenter Server 6.0

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

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:

Related Versions:

Take Our Survey

Support Assistant