• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 325
  • Last Modified:

SQL Server 2008 r2- Login failed for user 'sa' - account is currently lock

I got message on running application as follows

run-time error - 2147467259
login failed for user 'sa' because account is currently locked out. The system administrator can unlock it.

I have 3 database on server but only one database it is giving error,

Thanks in Advance.

Nitin
0
Nitin Shah
Asked:
Nitin Shah
  • 2
1 Solution
 
arnoldCommented:
The error is given on the database to which SA credentials are in use.
The other databases might be using other credentials.  
Depending on your setup, it seems that you may have account lockout policy in place and the SA user login attempts have exceeded that treshhold locking the account for the duration set in the password handling Policy.

Possible cause is user/systems on the LAn attempted to gain access to the sql server using the SA.
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
I have 3 database on server but only one database it is giving error,
Did you want to mean 3 Instances instead of 3 databases?

There's any other user with SA permission? If not, ask to your system administrator to change the Account Lockout Policy on the Local Security Policy (gpedit.msc).
0
 
Nitin ShahAuthor Commented:
No all database have user 'sa'.  but my problem solved after re-installing sql server.

Thanks

Nitin
0
 
arnoldCommented:
While it is common for some to go the reinstall route, one learns nothing from that experience while risking a significant catastrophe.

It is unnecessary to reinstall something that is not broken. My guess is that the lockout period ended by the time the reinstall completed and a reinstall does not and will not resolve the underlying issue that led to the lockout of the account.

Often the administrative user given sql login is only available in a mix mode configuration and provided the person remembered to add administrative account/accounts to the sql server (they can but do not necessarily have to be administrative on the server or the domain).
Using SSMS by the SQL Administrative windows account, you can connect to the database and unlock the sa account after determining the source of requests that led to its lockout and dealing with the ............. i.e. a compromised system with a virus that attacked your sql server .......
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now