Please verify what the error code is. If it is DS_BUSY (0xc00002a5) then you
got a write conflict.
You cannot really do much here. SAM updates lockout status on the user
account with an asynchronous task, and the write might collide with some
other write (most likely, another failed logon attempt is updating the
badPwdTime attribute).
What you should do is try to locate the application that is issuing the
logon requests that are causing the lockout, and make sure it uses the most
recent pwd.
--
Dmitri Gavrilov
SDE, Active Directory team
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"OzzY" <apexgore@yahoo.com> wrote in message
news:u3OATCM8HHA.484@TK2MSFTNGP06.phx.gbl...