Where exactly you see that? Does the service run under the local service account?
can you provide logs or error message?
Did you choose a special user to run the VMware Windows services?? Like vCenter, Identify Service etc?
If is not a user, we could have an issue with Inventory Service Database.
All depends on what you have in the logs. Please provide vpxd.log and also inv-svc.log or invsvc.log. With this we can provide more help.
PS: If you try to use the search option in the vSphere Client Tool you get an error??
It is showing up in the security event log
An account failed to log on.
Security ID: SYSTEM
Logon ID: 0x3E7
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Failure Reason: Unknown user name or bad password.
Sub Status: 0xC000006A
Caller Process ID: 0x984
Caller Process Name: C:\Program Files\VMware\Infrastructure\VMware\CIS\vmware-sso\VMwareIdentityMgmtService.exe
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This all started after I changed the password for this account, it is a domain account and none of the services are using this account to login with.
are you using that domain account to run Identity service?
If Yes, go to services.msc, select Identity service and update user's password in properties.
if you are not using windows account to run the service then try this - go to Windows Control panel --> Credential Manager and clear all saved passwords.
The identity service is using the local system account and I looked in the credential manager and there isn't any saved passwords.
Looking in the vpxd log I see this event
2016-05-30T08:22:39.055-04:00 [07116 error '[SSO]' opID=20341374] [UserDirectorySso] AcquireToken exception: class SsoClient::InvalidCredentialsException(Authentication failed: Invalid credentials)
2016-05-30T08:22:39.055-04:00 [07116 error 'authvpxdUser' opID=20341374] Failed to authenticate user <Domain account>
Did you find solution for the above issue? Last few weeks, i am getting exactly same message in windows event logs. Please let me know. THank you.
No i never found the solution to it. I opened a case with Vmware but they tried telling me it was a bug in the software causing that even though its not doing it on our second instance of vcenter on a different network. I even upgraded the software and its still doing it so theres no way its a bug.