VMware Cloud Community
enesem
Contributor
Contributor
Jump to solution

Unable to access server from vsphere client

Hi, Folks.

After being fine for a couple of weeks, now I am unable to access my server from vSphere client, I get an error of:

Call "ServiceInstance.RetrieveContent" for object "ServiceInstance" on Server "192.168.6.2" failed.

I have attached screenshots of the error message.

The pc and the server are on the same subnet, and the error is from multiple pc's that try to connect.

Please help !

NM

0 Kudos
1 Solution

Accepted Solutions
biokovo
Enthusiast
Enthusiast
Jump to solution

Then I think you must restart those services like vivari said.

If you cannot connect via ssh you must have console access. Then you can restart services or enable ssh to do it via ssh.

View solution in original post

0 Kudos
7 Replies
vivari
Enthusiast
Enthusiast
Jump to solution

hai,

Access the server via SSH and restart the services,,

service mgmt-vmware restart

service vmware-vpxa restart

then check the result.

0 Kudos
enesem
Contributor
Contributor
Jump to solution

Hi,

I use Teraterm to connect via SSH, but I got a "connection refused" error.

NM

0 Kudos
biokovo
Enthusiast
Enthusiast
Jump to solution

Additional info will be helpful.

Can you ping your server? Traceroute? Is it esx or esxi? Any firewall or router?

0 Kudos
enesem
Contributor
Contributor
Jump to solution

Yes, I can ping the server, I can also remote to my VM using remote desktop.

It's esxi 4.1 u1.

I am on the same subnet, there is no firewall or gateway to pass through.

NM

0 Kudos
iw123
Commander
Commander
Jump to solution

Hi,

Do you get the same error if you try from a different client workstation?

*Please, don't forget the awarding points for "helpful" and/or "correct" answers
0 Kudos
biokovo
Enthusiast
Enthusiast
Jump to solution

Then I think you must restart those services like vivari said.

If you cannot connect via ssh you must have console access. Then you can restart services or enable ssh to do it via ssh.

0 Kudos
enesem
Contributor
Contributor
Jump to solution

OK, solved, thanks for the help.

I used the local console, and restarted management agents and now I have access. I also enabled SSH for future use.

Many thanks for helping, it was quite obvious in the end.

NM

0 Kudos