Not sure if it needs to be restarted.Ģ3-03-05T11:16:14.575652-06:00 err vmdird Bind Request Faile d (127.0.0.1) error 49: Protocol version: 3, Bind DN: 'cn=Administrator,cn=Users ,dc=vc65,dc=local', Method: SASL 23-03-05T11:16:14.579785-06:00 err vmdird SASLSessionStep: s asl error (-13)(SASL(-13): authentication failure: client evidence does not matc h what we calculated. then after many hours of attempts i was able to upgrade to 6.5.0 from a depot file using exscli command, the client was still working on 6.5, I think my mistake was jumping from 6.5.0 directly to 6.5.0u2 as the windows client was still working on 6.5 and you say it still works on 6.5.0U1, I should have not jumped to U2. The SSO service is running in the management portal. I originally got this G5 server with 6.0. But only 4 hosts with ESxi 7.o are added to vCenter. Eight hosts with ESXi 7.0 and Four hosts with ESxi 6.5. I used the vdcadmintool to reset the admin account but no dice. I must downgrade the license and convert it into a 6.5 license so that it works for me in the 4 hosts with ESxi 6.5 version. No one else needs to go into it unless there is trouble with some older legacy servers. All I was thinking was if someone else on my team reset the password or if something changed. I tried the administrator account, not working either. When I tried to log into Vcenter with my AD admin account, it was not working. Now, we have a local administrator account that Veeam uses to connect to this center. This vcenter is in the process of being decommed and being moved to 7.0 on newer hardware. I get a bunch of emails from Veeam saying all backup jobs have failed for our VC 6.5 hardware for the night. Hello, so here is what I have been trying to figure out for the last 12 hours.

Esxi 6.5 licence