Suddenly getting "Could not connect to one or more vCenter Server systems" error message in vSphere Web Client

[SArmburger]

I am able to access my vSphere server via the obsolete VMware vSphere Client, but I am not able using the VMware vSphere Web Client (https://ServerName.Domain.local:9443/vsphere-client/#extensionId=vsphere.core.viHome.domainView). I could up until yesterday, but as of this morning, I receive the following error message at the top of the vSphere Web Client:

Could not connect to one or more vCenter Server systems:

https://ServerName.Domain.local:443/sdk

The web page displays normally enough with the exception of this error message at the top of the page, and zero vCenter Servers, Virtual Machines, Datacenters, etc. along the left hand side.

About VMware vSphere shows the following:

vSphere Web Client:        Version 5.5.0 Build 1441077

Client Integration Plug-in

Browser                            Chrome Version 35.0.0.214

Additionally, in the vSphere Client, the bottom panel shows the same two Recent Tasks all morning. I cancelled them both.  They re-appeared and they just sit there. There doesn't appear to be anything happening with these two tasks. There is no indication of any recent tasks in the vSphere Web Client.

Name: Check new notifications

Target: ServerName.Domain.local

Status: Queued

Details:

Initiated by: VMware vSphere Update Manager Check Notification

vCenter Server: ServerName.Domain.local

Requested Start Time: 6/10/2014 11:09:01 AM

and:

Name: Check new notifications

Target: ServerName.Domain.local

Status: Queued

Details:

Initiated by: VMware vSphere Update Manager Check Notification

vCenter Server: ServerName.Domain.local

Requested Start Time: 6/10/2014 10:09:01 AM

All of the virtual machines seem to be running just fine.

When I pointed my browser to https://ServerName.Domain.local:443/sdk, I got an empty white page.

I have reset ServerName.Domain.local

All instances of ServerName.Domain.local in this message refer to the same physical machine.

At this point, I am stumped. Can anyone point me to the next logical step?

[Jayden56]

Hi

Welcome to communities.

Could you please first unregistered and register a vCenter Server system with the vSphere Web Client installed as part of a vCenter Server Appliance,

you must use the admin-app command-line script rather than the Web-based administration tool.

[kojoasamoa]

Please go to Component Services, normally found under Computer Management, then Services and check if the VirtualCenter Server and VirtualCenter Management Web Services are running. When they are not running, you face some of these problems.

[wlingle]

I had this same problem and just fixed it.  I had originally installed the VMware vCenter Server Applicance.  I logged into the applicance at the https://serveraddress:5480 address to find the Server service was not running (this was even after a reboot of the appliance which I assumed would restart the service).  Anyway on the home page, just clicked the start button next to the Server service and all is well.  Kojoasamoa had a similar reponse that should work if you running vCenter on a windows box.

[karimrdi]

Thanks kojoasamoa, that did the trick for me!

[2cool2touch]

In my case, the DNS server wasnt working for some reason. Fixing DNS fixed the issue.