Forum Discussion

10101's avatar
10101
Copper Contributor
Feb 18, 2025

SQL Server Account locked out and password did not match?

Hi

I posted this discussion earlier today, but could not find it!  Perhaps I did not add a tag?  In any case, I am reposting it.

 

We have this situation that a SQL Server account has been having two different login failures recently.  The errors appear in the SQL Server log without much details.  
Wonder if any one had encountered the same situation and if it had been resolved?

The two different error messages are:

1.
Login failed for user 'sql_account_name'.Reason: The account is currently locked out. The system administrator can unlock it.  [CLIENT: ip_of_another_computer]

2.
Login failed for user 'sql_account_name'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]


Note: I replaced the actual account name and ip with sql_account_name and ip_of_another_computer respectively.


I found a query that displays the user account SQL agent jobs run under, but I did not see this SQL account.
Also, I checked linked servers, but did not see this account.
Furthermore, I checked Windows services of the two computers in the error messages, but I did not see that SQL account.
I did look Windows task scheduler, but do not think we can use SQL account as run under for a task.

Any idea or insight?

Thanks

 

sql server
  • AyushBansal's avatar
    AyushBansal
    Icon for Microsoft rankMicrosoft
    Feb 19, 2025

    This error generally occurs when someone tried logging in using this SA account multiple times with wrong password and the password policy is enabled due to which the account gets locked after a certain number of failed login attempts. To solve this, you can either change the password of the account or remove the password policy by disabling the enforce password policy option in the login's properties.

  • petevern's avatar
    petevern
    Brass Contributor
    Feb 19, 2025

    Here are some possible options to consider:

    • Application connecting ODBC or connection string
    • A scheduled task

    A useful troubleshooting step would be to run netstat -ano in the command prompt on both source computers. This will allow you to check if there is a connection attempt to SQL server. If a connection attempt is visible, the last column will show the Process ID (PID). You can then cross-reference this PID in Windows Task Manager to identify which application is attempting to establish the connection.

Resources