• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 11215
  • Last Modified:

ESXi new install: error connecting via vSphere Client: Call "ServiceInstance.RetrieveContent" ... what to do?

Hello Expert,

I just installed ESXi on my server (tower). Install ok!

Now, I am trying to access it (same subnet) via vSphere Client; but encountering some errors.

when prompted to login, I tried:

http://192.168.0.110
User name: root
Password: typed same password I used when setting host and also tried leaving it blank

then, when trying to connect, I get this prompt and error:

Prompt:
The server 'http://192.168.0.110' could not interpret the client's request
(the remote server returned an error: (404) not found)

error stack:
Call "ServiceInstance.RetrieveContent" for object "ServiceInstance" on Server "192.168.0.110" failed.

what can I do?

thank you experts..

regards,
0
epifanio67
Asked:
epifanio67
1 Solution
 
Danny McDanielClinical Systems AnalystCommented:
did you download the vSphere client from the ESXi host you just installed or get it from another location?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
just type the IP address or server name (providing it can do DNS, name lookup) in the vSphere Client box.

no need for http://
0
 
Danny McDanielClinical Systems AnalystCommented:
or use https://...  :)
0
Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

 
epifanio67Author Commented:
thank you experts...

the http was the problem...
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
it does give some wierd errors, if you type anything other than an ip address or server name!

(there's not much error trapping!)
0
 
juliovp01Commented:
In this case the vSphere client just need IP or Hostname. The software himself should know using which protocol is going to stablish the communication.
If you look into your VI Client logs you will notice something like this:
:ShowExcp:W: (DATE) Connection Error: The server '192.168.2.55' could not interpret the client's request. (The remote server returned an error: (404) Not Found.)
VirtualInfrastructure.Exceptions.ProtocolError: The server '192.168.2.55' could not interpret the client's request. (The remote server returned an error: (404) Not Found.
That at least should provide some hint for any other person having the same issues.
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now