I upgraded my vCenter 4.0 server to vCenter 4.1. After the upgrade I am seeing an error in the vCenter Service Status. The error is with com.vmware.converter, and the error is "Unable to retrieve health data from https://xxx.xxx.xxx.xxx/converter/health.xml". I rebooted after the upgrade. Anyone else seeing this, or know where I can look to find out what is wrong?
I have the same problem. I reinstalled the converter component on the vCenter server but it still shows up as an error for the converter in the service status and my conversions fail.
Anyone else managed to resolve this?
The following I found in release notes for Converter 4.2 for vCenter Server 4.1
vCenter Service Status for com.vmware.converter shows error During the vCenter Converter installation process, if you specify a short server name for vCenter Converter to register with the vCenter Server, the vCenter Service Status might display the error Unable to retrieve health data from [https://servername|https://servername/] for com.vmware.converter. Workaround: Use fully qualified domain name or IP address to register vCenter Converter with vCenter Server.
During installation, where I specify the FQDN a port is also specified - I was unable to set this to 443 as it was with my vCenter 4.0 installation. I have to set this to 80 before it is accepted and installation continues.
I'm also seeing this issue with Converter. I was also seeing an error message in Guided Consolidation under the Configuration Tab for vCenter Converter Server status but that seems to have gone away now. Originally I felt the two problems were directly related. I had originally installed Guided Consolidation before installing Converter - There is a dependency there where Guided Consolidation relies on Converter. I uninstalled both components and then installed Converter first, then Guided Consolidation.
[i]Jason Boche, VCDX #34, VCPx3, vExpert[/i]
Hi we have the exact same problem. Last night I updated the vcenter server to 4.1 and this morning I noticed the error
Vcenter server version
Error in vsphere Client
Actual Health status
So based on the actual Health status being greeen, I don't believe we really have a problem but it's messing up the alarms tab because it constantly shows an error
I believe all these strange errors are down to ADAM DB
especially in current 4.1 version of vCenter, 4.2 converter etc
No idea yet how to fix it, when it is "broken"
I have the same problem!!!
At least i still can use Converter without problems.
have VMware said something about this issue? I've not found anything yet.
Regards / Saludos
Patricio Cerda !http://www.images.wisestamp.com/linkedin.png!
Si encuentras que esta o cualquier otra respuesta ha sido de utilidad, vótalas. Gracias.
If you find this or any other answer useful please consider awarding points by marking the answer helpful or correct. Thank you.