July 16, 2008 at 8:48 pm
G'day All,
I am checking my Error Log for the SQL Agent and I have come across a job that I don't know what it is that is failing. The message just says:
Date16/07/2008 5:00:52 PM
LogSQL Agent (Current - 17/07/2008 12:01:26 AM)
Message
[165] ODBC Error: 0, Timeout expired [SQLSTATE HYT00]
and the one below it (same time - assuming same job):
Date16/07/2008 5:00:52 PM
LogSQL Agent (Current - 17/07/2008 12:01:26 AM)
Message
[382] Logon to server '(local)' failed (JobManager)
Does anyone know how I can find the job that has produced these errors? I have gone through all of the jobs and I can't find one that runs at 5:00PM.
This in in SQL Server 2000 SP4 on a Windows 2003 SP2 box .
Cheers.
July 16, 2008 at 9:47 pm
Hi,
The issue need not be related to only a job failure. As the SQL Server Agent is responsible for other tasks as well (schedules, alerts etc.,). However, the problem could be with the login (the service account) under which the SQL Agent is running. Have you checked this issue from that perspective..if the agent is running under a correct account????
[font="Verdana"]Renuka__[/font]
July 16, 2008 at 9:53 pm
Hi Renuka,
I have modified the SQL Agent today to have it running under a different account, but this occurred with the old account which has been running fine for years.
I guess what I am more after is how can I tell what object has caused the error? I can look through all schedules, alerts, jobs, etc, but is there an easy way of telling what object actually failed?
Gav
July 20, 2008 at 11:48 pm
Hi, you could use the msdb database and query from sysjobschedules to get the schedule, like if the job name is daily 5:30 then query :
select * from sysjobschedules where name like 'Daily at 5:30%'
in this way you could identify the job that runs at that particular time.
🙂
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply