Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Property IsLocked is not available for Login


Property IsLocked is not available for Login

Author
Message
sqldba4u
sqldba4u
SSC-Enthusiastic
SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)

Group: General Forum Members
Points: 117 Visits: 285
Hi,
Yesterday I ran into a strange situation. Users started telling that thay were not able to connect to their application using the sql account 'abcacc'. I checked logs and found several login failures from this account. When checking login property, it threw me error "Property IsLocked is not available for Login '[abcacc]'. This property may not exist for this object, or may not be retrievable due to insufficient access rights. (Microsoft.SqlServer.Smo)". I googled about it and executed below t-sql.

alter login abcacc with check_policy = off,check_expiration = off

Consequently, it started making successfull connections from this account. Gradually same issue was faced for other sql accounts on the instance and I executed the same script. Please note account was not locked.

Later 'Stack Dump' error was observed in the log just before the login failures started. Can someone please help me understand that above error came due to memory pressure or there could be other reasons as well? Wanted to know the root cause to avoid this issue in future.

Thanks in advance.

Regards
sqldba4u
patrickmcginnis59 10839
patrickmcginnis59 10839
SSC Eights!
SSC Eights! (872 reputation)SSC Eights! (872 reputation)SSC Eights! (872 reputation)SSC Eights! (872 reputation)SSC Eights! (872 reputation)SSC Eights! (872 reputation)SSC Eights! (872 reputation)SSC Eights! (872 reputation)

Group: General Forum Members
Points: 872 Visits: 5084
Just a possibility, you might want to check to see if your SQL user accounts have a password expiration policy set.


select name, is_policy_checked
from sys.sql_logins



(shamelessly stolen from this thread: http://www.sqlservercentral.com/Forums/Topic397068-338-1.aspx)

edit: just wanted to mention that I think this check is for SQL server user accounts that are NOT windows logins)

to properly post on a forum:
http://www.sqlservercentral.com/articles/61537/
SQLRNNR
SQLRNNR
SSC-Insane
SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)

Group: General Forum Members
Points: 21073 Visits: 18259
Sounds like the accounts were expiring.

You can checked for disabled, locked, or expired accounts using this script. You should probably monitor for this kind of thing.


SELECT sl.name,sl.is_disabled,sl.is_expiration_checked,sl.is_policy_checked,sl.modify_date
      ,LOGINPROPERTY(sl.name,'IsExpired') AS IsExpired,LOGINPROPERTY(sl.name,'DaysUntilExpiration') AS DaysToExpiry
      ,LOGINPROPERTY(sl.name,'IsMustChange') AS IsMustChange
      ,LOGINPROPERTY(sl.name,'BadPasswordCount') AS BadPasswordCount
   FROM sys.sql_logins sl





Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

sqldba4u
sqldba4u
SSC-Enthusiastic
SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)

Group: General Forum Members
Points: 117 Visits: 285
Thanks for the reply but how come all accounts on that instance were expiring at the same time. I want to know could this happen due to memory pressure or there could be other reasons as well.

Thanks.
SQLRNNR
SQLRNNR
SSC-Insane
SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)

Group: General Forum Members
Points: 21073 Visits: 18259
They were probably expiring at the same time because they were created at the same time.



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

sqldba4u
sqldba4u
SSC-Enthusiastic
SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)

Group: General Forum Members
Points: 117 Visits: 285
No, all SQL accounts were created on different dates.
SQLRNNR
SQLRNNR
SSC-Insane
SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)

Group: General Forum Members
Points: 21073 Visits: 18259
Did somebody alter their Expired property?

Has somebody altered the local account policy on SQL Server to have the accounts expired?

In short, the most probable answer is that something was changed to cause them to expire.



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

sqldba4u
sqldba4u
SSC-Enthusiastic
SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)

Group: General Forum Members
Points: 117 Visits: 285
It doesn't seem so. Is it anyway possible that it could be due to memory issue? I know its something unusual to ask but need to go thru all possibilities.

Thanks.
SQLRNNR
SQLRNNR
SSC-Insane
SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)

Group: General Forum Members
Points: 21073 Visits: 18259
Do you have any other reason to believe you have/had a memory issue?



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

sqldba4u
sqldba4u
SSC-Enthusiastic
SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)SSC-Enthusiastic (117 reputation)

Group: General Forum Members
Points: 117 Visits: 285
There were memory physical dump details logged in the error log just before login failures started.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search