Reason: Password did not match that for the login provided. 09:58:12.48 Logon Login failed for user 'sa'. (Better: If you have enough space for your ERRORLOG and are cycling the ERRORLOG at a regular interval, set it to Both failed and successful logins.)Ĭheck the SQL Server ERRORLOG file for login issues and track down who is behind the IP address in the error message. Change the password for the sa account to ensure nobody gains access to the server via this account.Įnsure that the option Failed logins only is enabled at server level in the in the Server properties - xyz | Security tab | Login auditing section.somebody is just having fun locking out the sa account. the hacker is unable to gain access again, which results in a lockout. the user using the sa account is unable to enter the correct password after n attempts, which results in a lock out. If you changed the Active Directory policy recently to lock accounts after n wrong password attempts or if you reduced the number of wrong password attempt to cause a lockout, then you might be encountering a locked sa account due to. it didn't matter if any script, program, user, system used a wrong password for the sa account. the hacker was able to enter multiple passwords for the sa SQL Login until he had access. the user's inability to use the correct password had no adverse effect on the sa account (No locking of sa account) If you previously didn't have an Active Directory policy for locking out accounts, then. Possible reasons for change in lockout behaviour
SQL SERVER SA ACCOUNT LOCKED OUT 2008 HOW TO
I discussed this setting in my answer to the question How to lock a sql login after N unsuccessful login attempts. One of them being Enforce password policy.
When you look at the General tab in the Login Properties of the sa account, you will notice different settings. Could it be that connection pooling doesn't require re-authentication? How is that possible? Update2: We realized that some of the threads in some applications kept working, even though other threads and other applications were encountering sa is locked message. We haven't set a policy so far, and we do not even know where are the policies. Start SQL Server services at last before you login SQL Server with SA account. And type command below to do later: Then stop SQL Server services and remove '-m' from the 'Start parameters' field. If you want to reset SQL SA password with command, just follow the command in step 1 for enabling SA account. Choice 1: Reset SQL SA Account Password with Command. Update: in this post it's been argued that a policy check can make this happen. Command or SQL password recovery tool, no matter with which one, you can reset SA account password for SQL Server 2014/2012/2008/2005. Why it has happened in the first place at all? What possible reasons caused it, and might cause it again? Was it because of an attack? We have no clue, and any help is appreciated. However, the more we search the less we find out about the reason behind this. Of course it can be solved in a minute of Googling around, via some tricks and scripts. Login failed for user 'sa' because the account is currently locked out. We watched the log today and found out that this was the message: Last night all of our systems failed and connections to the database kept dropping.
0 kommentar(er)
