Solved

Why can I not unlock a SQLServer User?

Posted on 2009-07-09
5
407 Views
Last Modified: 2012-05-07
I am the owner of my database and have remote desktop access to my virtual server (windows 2003) running SQL 2005.  I had three bad login attempts on one of my users and I a trying to "Unlock" the user.

On the DB Server, in SSMS, I navigate to the User under the Security->Logins.  I open the Properties of the user then select Status and I see "Login is locked out" checked.  I uncheck it, go change the password in the "General" section and then click OK.  No errors but when I go back into the Status of the user the user is still "Locked out".

Is there something else I have to change?
0
Comment
Question by:Bruce
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
5 Comments
 
LVL 4

Accepted Solution

by:
nasserd earned 250 total points
ID: 24815731
Try to OK for every item change; for example, uncheck the Locked Out status, then OK before resetting their password.

SSMS isn't good at reliably maintaining values -- so pair every value change with an OK.
0
 
LVL 1

Author Comment

by:Bruce
ID: 24815751
I get a "Change password failed for login..."
0
 
LVL 1

Author Comment

by:Bruce
ID: 24815778
Ooo, ooo, ooo, SSMS, so bad.

Got it.  In a round about way.  I unchecked "enforce" password policy, then unchecked "Lock out", then OK.  Then it worked.  I then went back in and rechecked "enfore..."
0
 
LVL 15

Assisted Solution

by:rob_farley
rob_farley earned 250 total points
ID: 24820046
Ah - the problem is that if you're enforcing password policy, that may include something along the lines of "You can't leave your password the same if you get unlocked".

So it's often best to turn off that password policy when you're playing with those settings.

Ultimately, you may prefer to use Windows Authentication, so that your Active Directory guys handle all the passwords, and people don't need to provide a password to be able to access SQL.

Rob
0
 
LVL 1

Author Closing Comment

by:Bruce
ID: 31601714
Thank you gentlemen!  

For those that follow  
The workaround is in comment: 07/09/09 12:09 PM, ID: 24815778

The explanation for the workaround is from rob_farley (07/09/2009 - 09:52PM CDT).

Thanks!!
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Introduction SQL Server Integration Services can read XML files, that’s known by every BI developer.  (If you didn’t, don’t worry, I’m aiming this article at newcomers as well.) But how far can you go?  When does the XML Source component become …
Introduction In my previous article (http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/SSIS/A_9150-Loading-XML-Using-SSIS.html) I showed you how the XML Source component can be used to load XML files into a SQL Server database, us…
Via a live example, show how to setup several different housekeeping processes for a SQL Server.
Viewers will learn how to use the SELECT statement in SQL and will be exposed to the many uses the SELECT statement has.

740 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question