Hello everybody! I really do not understand what's going on.
The latest vcenter 6.5 (clean installation from VMware-VIM-all-6.5.0-5705665.iso).
In the web-client I see
---------------------------------------
Could not connect to one or more vCenter Server systems: https://<vcenter-fqdn>:443/sdk
---------------------------------------
In https://<vcenter-fqdn>/pcs
---------------------------------------
503 Service Unavailable _serverNamespace = / action = Allow _pipeName = \\. \ Pipe \ vmware-vpxd-webserver-pipe)
---------------------------------------
In Windows, all services are started. Reboot and wait does not help.
Could this be due to the replacement of certificates through a certificate-manager (point 2 Replace VMCA Root Certificate with Custom Signing Certificate and Replace All Certificates)?
Set vSphere WebClient service to Automatic and restart it.
Post the logs from file vsphere_client_virgo.log from location C:\ProgamData\VMware\vCenterServer\logs\vsphere-client\logs\
No ideas?
Services you can find here
But as you aren't able to login, navigate in command prompt to C:\Program Files\VMware\vCenter Server\
service-control --list
service-control --status
Secondly, check permissions as in logs below I can see permissions and certificate errors.
2017-06-30T13:52:40.868+03:00 info vpxd[06388] [Originator@6876 sub=vpxCrypt] Failed to read X509 cert; err: 151441516
2017-06-30T13:52:40.878+03:00 info vpxd[06388] [Originator@6876 sub=vpxCrypt] Failed to read X509 cert; err: 151441516
2017-06-30T13:52:41.438+03:00 error vpxd[06340] [Originator@6876 sub=vmomi.soapStub[8]] initial service state request failed, disabling pings. error=HTTP Status:400 'Bad Request'
2017-06-30T13:52:41.438+03:00 warning vpxd[06340] [Originator@6876 sub=Default] Closing Response processing in unexpected state: 3
2017-06-30T13:52:41.523+03:00 error vpxd[06388] [Originator@6876 sub=AuthorizeManager] [ACL] Adding unresolved permission for user "VSPHERE.LOCAL\Administrator"
2017-06-30T13:52:41.523+03:00 error vpxd[06388] [Originator@6876 sub=AuthorizeManager] [ACL] Adding unresolved permission for group "SRVS\srvs_admin_vsphere"
2017-06-30T13:52:41.523+03:00 error vpxd[06388] [Originator@6876 sub=AuthorizeManager] [ACL] Adding unresolved permission for group "SRVS\srvs_admin_vsphere"
2017-06-30T13:52:41.523+03:00 error vpxd[06388] [Originator@6876 sub=AuthorizeManager] [ACL] Adding unresolved permission for group "SRVS\srvs_admin_vsphere"
2017-06-30T13:52:41.523+03:00 error vpxd[06388] [Originator@6876 sub=AuthorizeManager] [ACL] Adding unresolved permission for group "SRVS\srvs_admin_vsphere"
2017-06-30T13:52:41.523+03:00 error vpxd[06388] [Originator@6876 sub=AuthorizeManager] [ACL] Adding unresolved permission for group "SRVS\srvs_admin_vsphere"
2017-06-30T13:52:41.523+03:00 error vpxd[06388] [Originator@6876 sub=AuthorizeManager] [ACL] Adding unresolved permission for group "SRVS\srvs_admin_vsphere"
I am having the same issue!!!
Seems that everyone is having this problem with VCSA, but I have a fresh installation on Windows Server 2016 and this error is frustrating.
Neither I can see the WebClient service, seems that 6.5 version doesn't include it anymore (not sure), you can try to stop/start the WebClient services with these command lines in your vCenter server( as admin):
C:\Program Files\VMware\vCenter Server\vmon\vmon-cli --stop vsphere-client
C:\Program Files\VMware\vCenter Server\vmon\vmon-cli --start vsphere-client
But this doesn't work for me, still same 503 error!!!
Any ideas??
Hi, I have the same problem with vCenter Server 6.5 on windows 2012 R2, anyone? mulcas did you solve it?
Hi, yes I solved it.
My issue was particular, I had VMware tools installed but somehow it wasn't updated on the server, this was preventing the ESXi to sync the NTP service. In few words, make sure you have your NTP service synchronize among all your servers (AD, Database) that co-work with vCenter, and restart this service on the machines or restart the machines itself.
So, check NTP for ESXi --> VMs --> vCenter Server. And remember to check if VMware Tools is updated and running properly.
If this doesn't solve your issue, probably there is a problem with the vCenter Database... if you can, reinstall.
Cheers!