network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 4 months |
| seen | Jan 24 '12 at 12:07 | |
| stats | profile views | 1 |
|
Jan 24 |
awarded | Supporter |
|
Jan 22 |
awarded | Teacher |
|
Jan 21 |
comment |
SQL Server 2008R2 Logon failed Yes, there was a trigger. But noticed that it's not a logon trigger. Rather an after logon trigger attached to a table. I read your referenced post. You indicate status 2 & 5 are very similar. One difference is that status 2 could be for Windows or SS server authentication. Status 5 you write it only indicates login user is not known to SS. Is this a real distinction? I would not expect "Network Service" to be an SS user. All this said, my explicit question is/was is there anyway to know what trigger failed? If the answer is "no" and if prior commenter wants to so state, I'll accept it. |
|
Jan 20 |
comment |
SQL Server 2008R2 Logon failed @AaronBertrand Error: 18456, Severity: 14, State: 5 Another detail. I found one AfterLogin trigger on a table. I dropped that trigger this afternoon and since then, there have been no login failures for the mentioned NT account (or for any account). I can't yet explain why this is. The trigger was inserting data into a table including the system user. This NT account was being listed as one of the users as was the SA account and others. |
|
Jan 20 |
awarded | Student |
|
Jan 20 |
asked | SQL Server 2008R2 Logon failed |
|
Jan 20 |
answered | Restoring SQL Server database backup file for read-only access - is it possible to skip the ldf file creation? |
