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

vCenter Service Status displays an error for com.vmware.converter (1025010)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 62295Language:
Chinese (Simplified)JapaneseSpanishEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

After installing or upgrading to vCenter Server 4.1, the com.vmware.converter item in the vCenter Service Status page is displayed in red.

You see the error:

Unable to retrieve health data from https://VC servername or IP address/converter/health.xml

Note: For German customers, the vCenter Service Status message is:

Daten zum Systemzustand konnen nicht von https:///converter/health.xml abgerufen werden

Registering the Converter with vCenter Server by short name, FQDN, or IP address does not resolve this issue

In the vws.log file, you may see messages similar to:

Thread-34 ERROR com.vmware.vim.health.impl.ComponentSpec] Unable to retrieve health for com.vmware.
converter from any of its health URLs
Thread-34 ERROR com.vmware.vim.health.impl.XmlUtil] Error validating health from stream
ERROR com.vmware.vim.health.impl.XmlUtil] Invalid health data: org.apache.commons.httpclient.AutoCloseInputStream@705c358b
org.xml.sax.SAXParseException: cvc-complex-type.4: Attribute 'id' must appear on element 'message'.

Thread-16 DEBUG com.vmware.vim.health.impl.ComponentSpec] Setting up HttpClient for component com.vmware.converter and url https://192.168.1.6/converter/health.xml
Thread-16 DEBUG com.vmware.vim.health.impl.ComponentSpec] Set up login URL https://192.168.1.6 for component com.vmware.converter
Thread-16 ERROR com.vmware.vim.health.impl.ComponentSpec] Unable to retrieve health for com.vmware.converter from https://192.168.1.6/converter/health.xml

If you do not see the vws.log file errors and enable debug logging in the vws.log file, the vws.log file contains messages similar to:

DEBUG com.vmware.vim.health.impl.ComponentSpec] Setting up HttpClient for component com.vmware.converter and url https://xx.xx.xx.xx/converter/health.xml
DEBUG com.vmware.vim.health.impl.ComponentSpec] Set up login URL https://192.168.1.6 for component com.vmware.converter
ERROR com.vmware.vim.health.impl.ComponentSpec] Unable to retrieve health for com.vmware.converter from https://xx.xx.xx.xx/converter/health.xml

Unable to retrieve health for com.vmware.vcIntegrity from (IP address) /vci/downloads /health.xml.

Note: The URL https://xx.xx.xx.xx/converter/health.xml can be accessed via a web browser on the vCenter Server machine.

Resolution

This issue has been resolved in vCenter Server 4.1 Update 1. Download vCenter Server 4.1 Update 1 from the VMware Download Center.

Prior to vCenter Server 4.1 Update 1, this message may be caused by an SSL Certificate handshake issue. It does not appear to impact Converter functionality.

To work around this issue, try using a fully qualified domain name or IP address to register vCenter Converter with vCenter Server. This may help in some cases.

Alternatively, replace the thumbprint entry of Converter in the ADAM LDAP database with the vCenter Server thumbprint.

To replace the Converter thumbprint with the vCenter Server thumbprint:

Caution: This workaround has only been tested for configurations where vCenter Server and Converter co-exist on the same machine. Do not perform this workaround if vCenter Server and Converter are on different servers.

Notes:

To apply this workaround, you must must have ldp.exe binary or adsiedit.msc on your system (to read and update the ADAM data). You can download ldp.exe or adsiedit.msc from the Windows Support Tools or the Microsoft Download Center

Note: The preceding link was correct as of January 14, 2012. If you find the link is broken, provide feedback and a VMware employee will update the link.

In Windows 2008 server you can find ldp.exe under Server Manager > Roles > Active Directory Lightweight Directory Services > Advance Tools.

For adsiedit.msc, on Windows 2003 or Windows 2008, click Start > Run, then type adsiedit.msc.

To connect to the LDAP server running on vCenter Server using ldp.exe:

Install ldp.exe if it is not already installed, then open ldp.exe.

Go to Connection > Connect and enter the hostname of the vCenter Server to which you want to connect.

Go to Connection > Bind and enter authentication information. You can use the admin account.

To see all contexts of the ADAM server, go to View > Tree View. Do not fill anything in Base DN. Click OK.

To connect to the LDAP server running on vCenter Server using adsiedit.msc:

Install adsi.msc if it is not already installed, then open adsiedit.msc.

Right-click ADSI Edit in the MMC, then click Connect.

Under Connection point, in the Select or type a Distinguished Name field, enter DC=virtualcenter,DC=vmware,DC=int.

Windows 2008 only: Select the Computer radio button, then under Select or type a domain or server, enter the vCenter server name followed by 389.

Example: vcentername:389

Note the vmw-vc-SSLThumbprint attribute values of vCenter Server's SSL certificate:

Double-click DC=virtualcenter,DC=vmware,DC=int, then double click:

OU=Health,DC=virtualcenter,DC=vmware,DC=int

OU=ComponentSpecs,OU=Health,DC=virtualcenter,DC=vmware,DC=int

CN=<GUID>,OU=ComponentSpecs,OU=Health,DC=virtualcenter,DC=vmware,DC=int

CN=<GUID>.vpxd,CN=<GUID>,OU=ComponentSpecs,OU=Health,DC=virtualcenter,DC=vmware,DC=int

When you double-click the last node, you see a list of attributes under the object. Look at vmw-vc-SSLThumbprint and note the vmw-vc-SSLThumbprint attribute value.

Replace the vmw-vc-SSLThumbprint attribute values of Converter health component-spec:

Double-click DC=virtualcenter,DC=vmware,DC=int, then double-click:

OU=Health,DC=virtualcenter,DC=vmware,DC=int

OU=ComponentSpecs,OU=Health,DC=virtualcenter,DC=vmware,DC=int

CN=com.vmware.converter,CN=<GUID>,OU=ComponentSpecs,OU=Health,DC=virtualcenter,DC=vmware,DC=int

Note the vmw-vc-SSLThumbprint attribute value for backup.

Right-click CN=com.vmware.converter,CN=<GUID>,OU=ComponentSpecs,OU=Health,DC=virtualcenter,DC=vmware,DC=int and choose Modify.

Enter this data:

Attribute: vmw-vc-SSLThumbprint

Values: the vmw-vc-SSLThumbprint attribute value from step 3b

Operation: Replace

Click Enter.

Click Run.

At this point it may be neccesary to restart the VirtualCenter Server service and the VMware VirtualCenter Management Webservices. For more information, see Stopping, starting, or restarting vCenter services (1003895).

Note: This issue is also reported in the VMware vCenter Converter 4.2 for vCenter Server 4.1 Release Notes. For more information, see the Known Issues section.

Related Information

To enable debug logging for vws on vSphere 4.1:

Using a text editor, open the file log4j.properties.

Note: This file is located in C:\ProgramFiles\VMware\Infrastructure\tomcat\webapps\vws\WEB-INF\classes.

Change these parameters:

log4j.logger.com.vmware.vim=DEBUG

log4j.appender.LOGFILE.Threshold=DEBUG

log4j.appender.LOGFILE.MaxBackupIndex=1000

To enable debug logging for vws on vSphere 4.0.x:

Using a text editor, open the file log4j.properties.

Note: This file is located in C:\ProgramFiles(x86)\VMware\Infrastructure\tomcat\webapps\vws\WEB-INF\classes.

Change these parameters:

log4j.logger.com.vmware.vim=DEBUG

log4j.appender.LOGFILE.Threshold=DEBUG

log4j.appender.LOGFILE.MaxBackupIndex=1000

Notes:

Windows 2003: VWS.log can be located in C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\Logs.

Windows 2008: VWS.log can be located in C:\ProgramData\VMware\VMware VirtualCenter\Logs.

How to stop, start, or restart vCenter Server services
vCenter Service Status muestra un error de com.vmware.converter
vCenter Service Status 显示一条关于 com.vmware.converter 的错误
vCenter サービス ステータスに com.vmware.converter のエラーが表示される

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseSpanishEnglish

Attachments

Additional Resources

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

KB
•
Melhores práticas para instalar o ESX 4.0 e o vCenter 4.0 (1009080)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

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

Take Our Survey

Support Assistant