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 |
|
barnabeck
Posting Yak Master
236 Posts |
 Posted - 2011-10-10 : 03:34:36
|
| I just occasionaly checked the log-file of one of our servers (SQL 2005) and I see a login error (Error: 18456 Severity: 14 State: 5) that occurs every minute over the last months. The user is the domain administrator and he is trying to access from the local machine.How can I trace that process that is trying to access so desperatly?Martin |
|
|
Lumbago
Norsk Yak Master
3271 Posts |
Posted - 2011-10-10 : 04:08:22
|
| Have you looked through the sql server agent jobs and the scheduled tasks on the server?- LumbagoMy blog-> http://thefirstsql.com/2011/07/08/how-to-find-gaps-in-identity-columns-at-the-speed-of-light/ |
 |
|
|
barnabeck
Posting Yak Master
236 Posts |
Posted - 2011-10-10 : 04:31:17
|
| I looked through the jobs and there is no one that is scheduled every minute. Beside the fact that the ones listed in jobs are mainly owned by that same user (domain administrator) and they all are executed well, causing no login error. Is there a difference between tasks and jobs? |
|
|
|
Lumbago
Norsk Yak Master
3271 Posts |
Posted - 2011-10-10 : 04:50:53
|
| Task Scheduler is a windows service and has nothing to do with sql server in itself. Look for "Task Scheduler" in the windows control panel... You can also look in Windows Services and see if you find anything that could cause this. Since it happens every minute I'm pretty sure it would be either of those (windows service, windows scheduled task or sql agent job).- LumbagoMy blog-> http://thefirstsql.com/2011/07/08/how-to-find-gaps-in-identity-columns-at-the-speed-of-light/ |
|
|
|
barnabeck
Posting Yak Master
236 Posts |
Posted - 2011-10-10 : 06:25:11
|
| There aren't any tasks defined in the task scheduler, no service is assigned to that user, no job that wouldn't execute without problem... must be comming from somewhere else. Hmmm |
|
|
|
|
|
|
trace a login error