503 Service unavailable ++++

[SamuelBdos]

503 Service Unavailable (Failed to connect to endpoint: [class Vmacore::Http::LocalServiceSpec:0x000000cb473a61b0] _serverNamespace = /vsphere-client action = Allow _port = 9090)

This is nemsis.

I was running vCenter 6.0 with Veeam 9.0 on the same virtual machine.  Around the beginning of the year I noticed my backups were not running and this message appeared when I try to manage my virtual machines using the web client.

I have found little to no information on this error and decided to reinstall the vCenter.  I upgraded to vCenter 6.5.  The system worked for a day or two and then came the above error again.

I uninstalled the vCenter software restarted and reinstalled.  Worked for a while and then the same error.

I uninstalled all the software on the machine (including vCenter and Veeam) and wiped that machine and rebuilt it from scratch.  I installed vCenter 6.5.

No problem

I configured and added ESXi  host, no problem

Restarted no problem

I installed and configured Veeam and my backups.  So far no problem

I shutdown and exported the virtual machine as an OVA as a backup of the working system.

I rebooted and started the Web Client.   And again I am at the same place with the above message.

So my Question is "H E L P"

I have no idea where to go from here.  I have been looking at log files but outside of MS DTC errors I have found nothing to guide me to a solution.

SamuelBdos

[a_p_]

Welcome to the Community,

from what you explain this could be an issue with Security Group Policies.

Some accounts need to have e.g. "Logon Batch" permissions, and if a Group Policy removes these accounts you'll end up with a system that works for the time until the policies are applied again. Youll find the information in the documentation at VMware vSphere 6.5 Documentation Library

Note that the required information seems to be only available in the English version of the documentation!

André

[truwarrior10]

From C:\program files\VMware\vcenter server\bin run the service-control --status --all command and verify the services are running.

I had a similar issue. The accounts were not set to do not expire and were checked to have the user change the password at next login. I had to reset the local user accounts used by the vCenter services.  I then had to update the account passwords in vCenter, i.e. "c:\program files\VMware\vCenter Server\vmon\vmon - p eam" then enter the new password. I believe there was about 6 or so accounts I had to set.

[abhi_77]

HI All,

Steps

1. Login to vCenter Sercer Appliance

2.Example :https://192.168.0.8:5480/ui/services

3. Restart the VMware vSphere Web Client service

[Mrmandala]

Thanks, this worked for me