Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
helpme
Posting Yak Master
141 Posts |
 Posted - 2011-01-15 : 14:47:43
|
| We have an instance that is getting the following message in it's log: Login failed for user 'ABC'. [CLIENT: 99.99.999.999]Error: 18456, Severity: 14, State:16.This is an instance that I inherited, so I don't know why this user is in the db to begin with. It doesn't have any privileges on any of the db's. The client that is trying to connect is an application that is maintained by vendors, so it may be days before I can get this stopped. Is there anyway to keep these messages from being repeated in the SQL Server logs? It's putting out about 25 of these per second, so the log is going to get pretty big pretty fast. |
|
|
dataguru1971
Master Smack Fu Yak Hacker
1464 Posts |
Posted - 2011-01-15 : 15:38:38
|
You can temporarily turn off login auditing in the instance security properties. Last time I saw this was when we had a consultant who configured Red Gate with the wrong ID and it was constantly trying to reconnect for SQL prompt and monitoring.
Poor planning on your part does not constitute an emergency on my part. |
 |
|
|
helpme
Posting Yak Master
141 Posts |
Posted - 2011-01-15 : 15:53:59
|
| Thanks dataguru1971 |
|
|
|
|
|
|
error 18456 severity 14 state 16