Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, August 30, 2012 9:33 AM
Hi,
My account is getting locked out on a daily basis. I have seen that the DC logged an event saying Sharepoint tried to logon, but had an incorrect password. I am sure it is due to the passwords not being synced between DC Active Dir and Sharepoint as this has been happening since we changed our passwords.
Could someone tell me if you have to manually sync passwords, run an stsadm command to sync these passwords. I would of thought this was automated. Could it be I haven't got a service running which does this?
Can you help?
Thanks.
John.
All replies (7)
Monday, September 3, 2012 10:06 AM ✅Answered | 1 vote
Hi,
If you have not restarted your VM or server then SP will still accept old password. So first you update your password in AD then you need to update same password in sharepoint server as well.
stsadm -o updateaccountpassword -userlogin DomainName\UserName -password NewPassword -noadmin
Please follow this Kb article to update same for other service as well
http://support.microsoft.com/kb/934838
Hope i understood you correctly
Cheers, Hemendra-MCTS "Yesterday is just a memory,Tomorrow we may never see"
Wednesday, February 20, 2013 3:09 PM ✅Answered | 1 vote
Hi Dirk,
I had this issue a while back when we changed passwords. It still happens believe it or not. Some of the IT Support guys think the Active Directory sync isn't working correctly possibly...and it's a long shot...that machines are being left on over (i.e. not logged out and shiut down) night and used with old password when they come in in the morning.
I fixed the issue by manually updating the user password of the person who was locked out. You can use powershell:
or stsadm
http://support.microsoft.com/kb/934838?wa=wsignin1.0
I used the stsadm version and this reolved it for me.
Failing that Dirk just check you are not logged into any VMs on Domain. No services are running in your username (this is naughty and should never be done). No Application Pools are using your username.
Good Luck!
Hope this helps.
John.
Thursday, August 30, 2012 11:01 AM
No, you don't need to sync passwords manually.
Getting locked out of where? Windows? SharePoint?
Is your account being used as SharePoint Managed Account?
Rob Schifreen SharePoint 2010 Admin University of Brighton, UK
Monday, September 3, 2012 8:22 AM
Hi Robert,
Apologies. This should be Sharepoint 2007.
Windows - the account that is being locked out is my personal account on the Domain Controller which I use to log into my local machine. However, a V machine with Sharepoint 2007 is for some reason trying to access this account with an old password and locks the account.
Thanks.
John.
Tuesday, February 12, 2013 1:03 PM
Hi John,
could you solve your problem, yet? I´ve got a similiar issue with my SP 2010. Especially the next few days after a password change user accounts are getting locked out!
Thursday, October 31, 2013 10:04 AM | 1 vote
Hi John,
could you solve your problem, yet? I´ve got a similiar issue with my SP 2010. Especially the next few days after a password change user accounts are getting locked out!
Since we changed the account lockout threshold policy to 11 attempts everything works fine...
Wednesday, March 4, 2015 4:41 AM | 1 vote
I changed my password this morning and experienced a similar problem. The issue was that the Visual Studio Test Controller service was set up to run with my credentials. The recovery settings sent it into an infinite loop and the service tried to log onto the domain with the incorrect credentials every couple of milliseconds. As a result my max login attempts were exceeded very quickly. The domain admin kept resetting the unsuccessful login counts, however I just could not compete with the speed of the Visual Studio Test Controller trying to log into the domain controller. It was a bit like getting handed a piece of paper with "Please turn over" written on both sides and was quite amusing initially. Kind admin eventually logged in and altered the logon settings, this fixed the problem.