Sql Server Job Did not Run

We have a Scheduled Job which runs daily at 12:01 am. But on Friday it did not run. I checked the Sql Server Logs, but could not find anything related.

In the event viewer I could find "The browser service has failed to retrieve the backup list too many times on transport DeviceNetBTTcpip{..........}. The backup browser is stopping." at 11:58:33 pm the previous night.

Kindly let me know what could be the reasons: I'm sure there was no server restart & services are enabled to run automatically.

Rgds Mohan Kumar VS

asked Mar 22 '11 at 12:11 AM in Default

Mohan Kumar
204 ● 12 ● 18 ● 20

(comments are locked)

5 answers:

A few possibilities:

Is the job enabled?
Is the job's schedule enabled?
Have you checked the SQL Agent log to ensure the service was actually running at that time? (You say you're sure but you don't say how you're sure.)
Did your clocks go back or forward around that time? That can mess things up.

answered Mar 22 '11 at 06:35 AM

David Wimbush
4.2k ● 25 ● 29 ● 31

Thanks. 1. The job is enabled. 2. The job is also scheduled. 3. Kindly let me know how to ensure that the service was actually running at that time. 4. There were no clock resetting....

Mar 22 '11 at 11:41 PM Mohan Kumar

I checked the service using Sql Server Agent log

Sql Server Agent Error Log: Date 3/18/2011 6:48:36 AM Log SQL Agent (Archive #4 - 3/19/2011 6:45:00 AM)

Message [129] SQLSERVERAGENT starting under Windows NT service control

Mar 22 '11 at 11:43 PM Mohan Kumar

So that confirms the SQLAgent service was started at 06:45 but look further back in the log. Every time the service starts it starts a new 'Current' log and archives the existing log, so you want to start with the archive that starts at 06:45 on the 17th and scan forwards for 24 hours.

Mar 23 '11 at 12:23 AM David Wimbush

Yes, thats correct. But there are no events in the log file at 12:01 am (the job's scheduled time).

Mar 23 '11 at 02:09 AM Mohan Kumar

Jobs running aren't in the error log. Only the startup and stopping of the service and exceptional events like errors. I meant that you need to look through the error log from the restart on the 17th to the restart on the 18th and make sure there's no sign that the service was stopped at 12:01 on the 17th.

Mar 23 '11 at 04:29 AM David Wimbush

(comments are locked)

Has the job run successfully since then?

Have you rebooted the server recently?

Has the infrastructure changed recently?

Does http://support.microsoft.com/kb/135404 fit / help?

answered Mar 22 '11 at 06:39 AM

ThomasRushton ♦
29.1k ● 6 ● 9 ● 36

Yes, the job is running successfully after that particular day. The server re-starts everyday at 06:45 am... The job is scheduled at 12:01 am. The infrastructure didn't change recently.

Mar 22 '11 at 11:44 PM Mohan Kumar

(comments are locked)