Hello All,
We have a service account login issue in vCenter. Account gets locked frequently and we have to unlock each time. Not sure of the issue.
14-08-25T17:16:35.989-04:00 [04616 verbose 'Default' opID=b765de9b] [VpxVmomi] Invoke error: vim.SessionManager.login session: 5204aa89-f750-8298-1310-5f8dadc2543b Throw: vim.fault.InvalidLogin
2014-08-25T17:16:35.989-04:00 [04616 verbose 'SoapAdapter.HTTPService' opID=b765de9b] User agent is 'Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 2.0.50727.3655)'
2014-08-25T17:16:35.989-04:00 [04616 verbose 'SoapAdapter.HTTPService' opID=b765de9b] HTTP Response: Complete (processed 584 bytes)
2014-08-25T17:16:35.989-04:00 [04616 info 'Default' opID=b765de9b] [VpxLRO] -- FINISH task-internal-3518975 -- -- vim.SessionManager.login -- 5204aa89-f750-8298-1310-5f8dadc2543b
2014-08-25T17:16:35.989-04:00 [04616 info 'Default' opID=b765de9b] [VpxLRO] -- ERROR task-internal-3518975 -- -- vim.SessionManager.login: vim.fault.InvalidLogin:
--> Result:
--> (vim.fault.InvalidLogin) {
--> dynamicType = <unset>,
--> faultCause = (vmodl.MethodFault) null,
--> msg = "",
--> }
--> Args:
-->
--> Arg userName:
--> "r1-core\xxxxxx"
--> Arg password:
--> (not shown)
-->
--> Arg locale:
These are some logs with error messages. Please have a look and see if someone can help me with this.
Thank you,
vamsi.
The password for this account was changed recently ? Check this KB article for some more tips: VMware KB: Active Directory account locks out due to repeated failed login attempts from vCenter Ser...
Hi Richardson Porto,
Thank you for checking, as per above KB my issue pointed to a DB that we are using for citrix provisioning.
Thanks,
vamsi.
Hi Richardson Porto,,
yes password has been changed recently for this account we are having issue, But now we are unable to find where it is coming from. Since this service account is being used at many places.
Thank you,
vamsi.
Take a look at Security Log in your domain controller for failed logon attempts for the vCenter service account... but you may need enable a GPO to audit logon events first.