Vcenter 4 error with Performance overview tab and health status tab

[Joshua_Mally]

Mine is a new Setup with ESX 4 and Vcenter4. In Vcenter4 when I go to the performace overview tab for a ESX server, i dont get any data however the page shows an error:

ERROR

The requested URL could not be retrieved

The following error was encountered:

• Connection Failed

The system returned:

(111) Connection refused

The remote host or network may be down. Please try the request again.

This same error shows up for Health status tab too however all the other tab are working fine. The Vcenter Plug-in are installed on the vcenter.

What could be wrong guys???

---Joshua

[admin]

Did you check if it's this?

http://kb.vmware.com/kb/1010725

[Joshua_Mally]

Thanks for the quick response. There was no rename of the vcenter server however I did check the extension.xml files and they have the correct hostname values.

Also just for info, im using SQL 2008 for DB for Vcenter.

[savoy6]

Did youfind a resolution for this issue. I am having the same issues and the xml files are correctly labled.

Savoy6

[Joshua_Mally]

Issue resolved. Had to set Vcenter to bypass the local proxy server and then restart the vcenter services

[savoy6]

Do you recall the ports you had to open for this to work. We have a proxy server as well, but I do not want to open all ports.....seems like you just had the vCenter server completely bypass the proxy?

Thanks,

Savoy6

[cnewstrom]

I was having the same issue. After finding a similar issue and solution listed for VDM, I decided to try the same thing for my VIC and it seems to have worked.

Try adding this registry value:

HKLM | SOFTWARE | VMware, Inc. | VMware Virtual Infrastructure Client | 4.0

New value type: REG_MULTI_SZ

Name: “BypassProxy”

Value: <your proxy server name or IP>

Then restart your VI Client.

Hope this helps ...

[cnewstrom]

Update to my post above:

I was curious about how and if my registry setting above actually worked, so I deleted the value from my registry and restarted the vSphere Client.

For some reason, the two tabs continue to work. I'm left unsure as to whether the registry setting did anything at this point. I can only report the results of having the two tabs work after having set the key and restarted the client.

If anyone else tries what I mentioned above, I'd be interested to see what the results are.

[cnewstrom]

After further testing I found that the registry entry above doesn't work. Don't use it.

The only consistency I could find with my configuration was as long as IE was set to "Automatically detect settings" under Internet Options | Local Area Network (LAN) Settings on my local (XP) workstation, the two tabs would not work.

This was due to a configuration on our local SQUID (proxy) server.

[SchulieBug]

Could you explain how you bypassed the proxy for vCenter? The solutions mentioned do not work, and i would very much like to user the full possiblilities via a remote viclient.