The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Error after upgrading to vCenter Server 5.x: com.vmware.converter alert unable to retrieve health data (2006132)
- 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.
To remove the remaining vCenter Converter attributes from the ADAM database:
- 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).
- 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.
- Remove the Converter folder, which is located at:
C:\Program Files\VMware\Infrastructure\VirtualCenter Server\extensions\com.vmware.converter
- Download the
cleanup.class.gzfiles which are attached at the end of this article.
- Using the
gunziputility, 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
PATH_ROOTvariables in the
cleanup.batfile. Update the variables to reference your vCenter Server install directory accordingly.
- Open a command prompt and run these commands to remove Converter and Update Manager attributes from the ADAM database:
cd "C:\Program Files\VMware\Infrastructure\VirtualCenter Server"
You see output similar to:
Deleting components of type com.vmware.vcIntegrity from CN=FD75D28F-CC3A-4638-8185-EEBC998DA14F,OU=ComponentSpecs,OU=Health
- 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).
- Stopping, starting, or restarting vCenter services
- Common vCenter Server and vSphere Client Windows paths
- Manually backing up and restoring the vCenter Server 4.x and 5.x ADAM instance data
- Connecting to vCenter Server using the vSphere Client fails with the error: Invalid URI: The hostname could not be parsed
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.