Re: Problem after sa password changed.

Thanks a lot. I found the process and problem solved.

"Russell Fields" wrote:

Chen,

You probably need to do a Profiler trace for login attempts or turn on
tracking of failed logins so that they show up in the Event Log. It sounds
like some program (or someone) is repeatedly trying to log in using the old
password.

I would suspect that this is a program that at some point was set up to
login using 'sa' and the 'sa' password. Now that the password has changed,
when the program attempt to run it repeatedly fails to login and the SQL
Server finally disables the 'sa' account. Until you find what or who is
responsible it will continue to happen.

Or, if you are on SQL Server 2005 you can rename sa to some other name.
This may complicate your life in some other way, but the failed attempts
will no longer disable your sa account, since you will no longer have an
'sa', but only the new name.

As an FYI, I only login as 'sa' once or twice a year. Setting up a Windows
account with sysadmin rights for my use is a whole lot safer.

RLF

"Chen" <Chen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:83C3F031-3A9A-4BFE-AAE8-FBAE961678E7@xxxxxxxxxxxxxxxx
Hi All,
According Internal/External audit and security purpose, in our production
SQL instance, I changed sa password about three weeks ago.
Its working fine until this morning, when I try to use sa login to SQL, I
got following error message:
Cannot connect to PRDB-OLAP\OLAP Login failed for use 'sa' because the
account is currently locked out. The system administrator can unlock it.
(Error: 18486).
In the Login Properties window, Status show Login is locked out.
I use windows login and un-select Login is locked out button than I can
login use sa account. But after around one hour, the sa account locked
again.
So I un-locked it for three times already, not sure if anyone can help me
to
solve this problem permanent?

Thanks!
Chen




.

Loading