Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have a VMware ESXi server which has been up and running for nearly 200 days. The past few days, when I try to connect to it using the VMware vSphere Client, I am unable to connect. After entering my username and password, I see the little spinning wheel and the status line say "Connecting..." and then "Loading Inventory...", and then I receive an error message:

Error Message Screenshot

The server 'my.host.name' could not interpret the client's request. (The remote server returned an error: (503) Server Unavailable

Call "ServiceInstance.RetrieveContent" for object "ServiceInstance" on Server "my.host.name" failed.

I am able to SSH in to the VMware ESXi server. All virtual machines seem to be up and running fine, so I want to know beforehand if I need to bring them down for maintenance!!! If methods proposed in your answer would interfere with running VMs please clearly state that so I know to prepare for downtime. Thanks!

How can I resolve this error condition on VMware ESXi?

(I'd post the version number but I don't know how to get it without the vSphere console!)

EDIT: Roughly a month after I asked this question, the server inexplicably rebooted itself. I don't know if it panicked or what happened... but after it rebooted, this problem was gone. So I can't test / confirm any of the answer unless the problem reappears (which I hope it does not!)

share|improve this question
add comment

4 Answers

This VMware KB article seems to match your described symptom. Verify that your DNS is up and running from the ESXi server's point of view.

Option 2: Can you verify, that your vCenter Server is up, and the service is started?

share|improve this answer
    
Well, it sure seems to match except that it says "it is not possible to connect to the ESX host using vCenter Server [...] for 30-40 minutes" and it's been working fine in my case for ~200 days... Also, DNS is working... –  Josh Sep 25 '11 at 16:23
    
You wrote that you could ssh into the server. Did you verify that DNS is working on the server? In this communities.vmware.com/message/1316434 thread a guy had identical problem as you describe. And it was DNS problem :). –  Paweł Brodacki Sep 25 '11 at 16:49
    
When I ssh in, I see /etc/resolv.conf does contain a nameserver line, and I can ping both google.com as well as the hostname of my server, so I'm reasonably sure DNS is workig. I don't have a vCenter server, only a single ESXi server. –  Josh Sep 26 '11 at 12:36
    
If you can ping them by name, then DNS does seem to work. In that case, there may be nobody listening... Take a look at kb.vmware.com/selfservice/microsites/… and see (netstat -in) if anything is listening on the ports, the client connects to. You may need to restart management service. –  Paweł Brodacki Sep 26 '11 at 12:58
add comment

You need to restart the vmware management services. Luckily, this is easy (since you have SSH access) and non-impactful to the virtual machines.

In a nutshell, SSH to the esx frame as root and then run one of the two following commands (depending on if it is esx/i):

For ESX:

service mgmt-vmware restart

For ESXi:

/sbin/services.sh restart

See this article for full details

share|improve this answer
    
Thanks. This probably would have solved the problem! Sadly the server crashed a couple weeks ago and the problem is gone now. –  Josh Nov 3 '11 at 12:21
add comment

I Solved the issue by uninstalling widecap ServiceInstance.RetrieveContent Error

share|improve this answer
add comment

I received this error right after my successful upgrade of vcenter 5.0 to 5.1. I noticed several alerts (under EVENTS (tasks & events)) within vcenter from service accounts that I had setup in the past for various items (kaspersky vsheild and orion syslog svc accounts) that were showing access denied. I added these accounts to the local administrators group on vcenter and my problems went away.

Before I discovered this however to provide myself a workaround I would simply restart vmware server service and then I could log in no problem and access vm consoles. After 5 minutes or so the consoles would go black and I could no longer access them. If I logged out and tried to go back into vcenter I would get this error:

Call "ServiceInstance.RetrieveContent" for object "ServiceInstance" on Server "my.host.name" failed.

So the rule is if you can get into vcenter go check the EVENT logs and see if there are any access denied alerts. If there is add these accounts to the local admin group on vCenter.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.