Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Error after upgrading to vCenter Server 5.x: com.vmware.converter alert unable to retrieve health data (2006132)

Symptoms

  • After upgrading to vCenter Server 5.x, the vCenter Service Status shows an error similar to:

    com.vmware.converter alert unable to retrieve health data from https://vcenter_servername.domain:port/converter/health.xml

  • This issue occurs if vCenter Converter is not uninstalled from the vCenter Server before upgrading to vCenter Server 5.x. However, uninstalling vCenter Converter from Add/Remove Programs after the upgrade to vCenter Server 5.x may not resolve this issue.

Cause

This issue occurs if vCenter Converter is not uninstalled before upgrading to vCenter Server 5.x. This can also be caused by old links left behind in the ADAM database after the upgrade.

Resolution

To work around this issue, uninstall vCenter Converter from the Add/Remove Programs on the vCenter Server, then remove the remaining vCenter Converter attributes from the ADAM database.

To remove the remaining vCenter Converter attributes from the ADAM database:

  1. Back up the vCenter Server ADAM database before proceeding.For more information, see Manually backing up and restoring the vCenter Server 4.x and 5.0 ADAM instance data (1029864).

  2. Stop the VirtualCenter Server service. For more information, see Stopping, starting, or restarting vCenter services (1003895).

    Note: Stopping the VirtualCenter Server service also stops the VirtualCenter Management Webservices service and the vSphere Profile-Driven Storage service.

  3. Remove the Converter folder, which is located at:

    C:\Program Files\VMware\Infrastructure\VirtualCenter Server\extensions\com.vmware.converter

  4. Download the cleanup.bat.gz and cleanup.class.gz files which are attached at the end of this article.
  5. Using the gunzip utility, unzip the files into this folder:

    C:\Program Files\VMware\Infrastructure\VirtualCenter Server

    Note: If the install directory of the vCenter Server is different in your environment, you must modify the _JAVA and PATH_ROOT variables in the cleanup.bat file. Update the variables to reference your vCenter Server install directory accordingly.

    If executing this in a vCenter Server 5.5 environment, change the _JAVA variable within the cleanup.bat file to:

    SET _JAVA="C:\Program Files\Common Files\VMware\VMware vCenter Server - Java Components\bin\java.exe"

  6. Open a command prompt and run these commands to remove Converter and Update Manager attributes from the ADAM database:

    For Converter:

    cd "C:\Program Files\VMware\Infrastructure\VirtualCenter Server"
    cleanup.bat com.vmware.converter


    You see output similar to:

    Deleting components of type com.vmware.vcIntegrity from CN=FD75D28F-CC3A-4638-8185-EEBC998DA14F,OU=ComponentSpecs,OU=Health

  7. Restart the VirtualCenter Server service, the VirtualCenter Management Webservices service, and the vSphere Profile-Driven Storage service. For more information, see Stopping, starting, or restarting vCenter services (1003895).

Additional Information

To be alerted when this article is updated, click Subscribe to Document in the Actions box.

See Also

Update History

06/28/2012 - Added additional cause and Note with output from command. 02/07/2013 - Added vCenter Server 5.1.x to Products

Attachments

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

  • 48 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)
  • 48 Ratings
Actions
KB: