Tuesday, March 6, 2012

2005: Disabled SQL Login

Is there something that would cause a SQL Login to get disabled

automatically? The login was used successfully yesterday but today we

were getting an error:

Login failed for user '<sql login>'. Reason: The account is disabled. [CLIENT: ipaddress]

Perhaps someone accidentally disabled this but that sounds unlikely.

I didn't see anything in the log about the account getting disabled.

Michelle

If you run

select * from sys.server_principals where name = '<sql login>'

You should be able to check to see if the login actually is disabled and what the last modified date is. This way you can check to see if it was actually changed.

Which log did you check? I believe that if you enabled trace for this, you should have received an event when the login was altered as well.

Sung

|||I had already enabled the login - the 'disabled' checkbox was checked

so I'm fairly certain that it really was disabled. The log file that

showed the error when the login was used to log in to the database was

the SQL Server error log.

I'm just trying to figure out how it got disabled and the only thing

that I can come up with is that someone did it accidentally.|||

The only thing I can think of that would cause something similar is when the account gets locked out.

But I believe the warning message is different and the control panel would show that the account is locked, not disabled.

I would guess the account was disabled by accident. You may want to create a trace for this action so you can monitor and audit this in the future?

Sung

|||

Logins are not disabled automatically and the action of disabling a login does not issue a log entry. Someone must have explicitly disabled the login. Was this login created by some application or was it a regular user login?

Thanks
Laurentiu

No comments:

Post a Comment