Jobs are not running 1

[mkal]

I have a sql job that is scheduled to run every day at 12:10 a.m. This job has successfully been run since it was created up until now.

There is no job history at all for 10/15/2006 & 10/16/2006, the job is enabled, the schedule is enabled and the SQL Server Agent was runnning and still is. There is nothing in the SQL Error Log (10/16/2006) that points to any problems and there were no sql SQLAGENT.OUT/SQLAGENT.1 files for those dates. Also, there was nothing in the Event Log for either of those dates during the time the jobs were suppose to execute.

It's not they they started and then failed its's that they never started period.

Anybody else experience anything like this? Any insight into why would be appreciated.

Thanks!

 

[sqlcasey]

Check the event viewer application log on the server - filter by SQL Server processes, look for errors around the date/time job didn't run

 

[mrdenny]

Can you start the job manually?

Sounds like the agent might have hung. Try restarting the agent.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[mkal]

I have a number of SQL errors listed per/sqlcasey recommendations but none of them occur during the time that the job is supposed to run, they span times from 3:06 a.m. - 4:08 a.m. for the 15th - 16th. They all deal with failed backups.

I can start the job manually and it does run. I don't think it's the SQL Agent because there were two other jobs, one that ran 5 min. before and the another 10 min. after this job. Frankly I'm confused as hell but what the heck I'll stop and restart the agent.

Is there anyway the job history can be deleted other than right-clicking the job >>> highlighting all the jobs and click the "Clear All" button. There is job history for this job from 10/14/2006 back to 8/16/2006 but not one thing for 10/15/2006 or for 10/16/2006 despite the fact it's enabled to run ever day.

Any other ideas or more info you need?

Thanks

 

[mrdenny]

Did the schedule get disabled some how?

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[mkal]

It's taken me most of the day but I found out what had happened. It wasn't the SQL Agent that had hung it was the process itself. It had two open transactions that would not commit (for whatever reason I don't know yet). I had to login into the server as the account running the job before I could see the open transactions. Once I rolled back the transactions the job history came up for 10/15/2006, that job had been running for over 38 hrs and that's why there was no history showing it was never being written as long as the processes were runnning.

Thanks for the ideas though I think it got me pointed in the right direction.

 

[sqlcasey]

mkal, come to think of it, i've had this problem before too, but it's been a while

i run this stmt to see what jobs are running on my server:

USE msdb exec sp_help_job @execution_status = 1