Has anyone seen this error when trying to re-organize columns inside of their vSphere Client?
If I click on my cluster > Virtual Machines tab > then click on the "Names" column to order by name, I get the above error message
My VMware VirtualCenter Management Webservices are started under one of my service accounts
Have you changed the hostname or domain membership of your vCenter server ? Did you already restarted the VirtualCenter Management Webservices ?
Yes I have restarted the service with no luck
Since I have worked for the company the domain name has not changed, nor the name of the vcenter server, is there anything I can do to try and fix this ?
My VMware VirtualCenter Management Webservices are started under one of my service accounts
Hopefully this is the same account as the one used for running the VMware VirtualCenter Server service? Or?
/Rubeck
Yes they are both using the same account, I have some further information, if I select a host within the cluster and go to virtual machines and click on the name column, it re-orders no problems, if I select the cluster then go to virtual machines, and click on name, I get the above error.
bump, any ideas on this one guys?
Hi again, Zade..
If you click on the data center level do you see the same error here also?
Selecting a single host does not show this message, right? And that goes for all hosts within the cluster.. ?
If restarting various agents doesn't work it then sounds a bit like an issue within the vCenter DB... If you have the option maybe you could try to create a new datacenter/ cluster and dump your hosts into this?
/Rubeck
Hello Zade,
in the client open vCenter Advanced settings and verify you have correct entries in these two keys:
VirtualCenter.VimApiUrl
https://<FQDN of you vCenter server>:443/sdk (The URL used for VIM API or vSphere Client access to this vCenter instance)
VirtualCenter.VimWebServicesUrl
https://<FQDN of you vCenter server>:8443/vws (The URL used to access supplemental vCenter web services)
Thank you I will check this and let you know my findings
Hi vNex
I have taken a look and at the moment it is the IP address of the server which is showing in the above, do you think this is why I am having issues because it is struggling to resolve by name?
In the error message it refers to the name of the server, rather than the IP address
Rubeck, I just noticed on our live vCenter server that the web services are started with a "webservices" account for vmware (service account) and our vCenter service is on a vmware vcenter account? Could this be the problem, should both accounts be on the same service account?
Hi,
it should work with IP also if its correct ... although I am not convinced it help try and replace value with FQDN.
As other solution unless is not recommended ... try to switch from service account to Local System for all the services configured with service account.
thanks vnex, yes the IP is correct, I was abit worried about losing access if I were to change to the full FQDN, or potentially causing any issues with vCenter.
Do you know why anyone would have a seperate service account for the web management service? we also have an additional DSN for web services which I have never seen (this is only in our live environment
if you are using Windows authentication on ODBC connection your domain account configured for Webservices must have administrative privileges on the vCenter Server DB!
So you should use same (domain) service account for both vCenter and Webservices !
