error: Cannot access the health service

[etamir]

Hi,

Background: vCenter 4.0 build 162856, managing ESX hosts vSphere 4 U1 build 208167...

I am having a strange error message when trying to view Hardware Status for ESX Servers:

When I press any one of my hosts I get this error

I have tried this with several different users including local administrator and domain admins. verified the permissions and roles as well...

even created a new local user and gave it administrator role, still no dice. (quite annoying)

Also When accessing the vCenter Services Status icon on the vCenter get this, which very possibly related...:

Any suggestions?

I have already tried the below KB and it didn't help....

http://kb.vmware.com/kb/1020288

[Troy_Clavell]

try this... I ran into this issue a few weeks ago.

http://kb.vmware.com/kb/1018203

[etamir]

Hi Troy,

Thanks for the quick reply...(that was FAST)

anyhow, we haven't upgraded the vCenter, it is installed from scratch...so the KB doesn't apply.

Any other suggestions?

[Troy_Clavell]

how bout this?

http://kb.vmware.com/kb/1018993

[etamir]

We are not using custom ssl certificates as well....

[Troy_Clavell]

I say upgrade vCenter to atleast U1. You should never have a vCenter version lower than the hosts you are managing. This may fix the problem. I would say, if you can, just go to U2.

[pcerda]

Hi,

It's not supported to manage ESX/ESXi hosts using a lower version of vCenter Server.

You should upgrade vCenter to at least the same version used by ESX host (4.0U1).




Regards / Saludos

-

---

Patricio Cerda !http://www.images.wisestamp.com/linkedin.png!

VMware VCP-410

Join to Virtualizacion en Español group in Likedin

See My Blog

See My Linkedin Profile

-

---

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.

[etamir]

That would be my thoguht as well, however I checked this in the vSphere compatability matrix and it seems to be supported to have vCenter 4.0 managing ESX4U1. I do think that is should always be the other way around as this is the normal way of upgrade...first vCenter then all the rest. But the customer is not will to do 2 phases U2 then 4.1 so they would like to go directly to 4.1 but this will require new Win2008R2 installation as their current vCenter is on 32bit OS...

So, I am pretty sure upgrading vCenter is worth the check but not in the customer scope currently. (unfortunately).

I wonder if there is a tweak I can do or something to make it wirk again....