none
SQL Server Agent Job is not running as per schedule RRS feed

  • Question

  • I have a job that is supposed to run every 6 AM.  It was running last week but not this morning. 

    The big problem is that there are no error messages what so ever. I checked Agent History, SQL server logs and Windows system logs.

    I checked the schedule and it is set to run everyday and there are no limits on how long it is supposed to run and it is enabled.

    Did anyone get this problem before?



    Monday, March 19, 2012 1:10 AM

Answers

  • Hi,

    Sometimes there are valid reasons a job will NOT kick-in on the scheduled time. Sometime ago, our database full backup job didn't start on time and in fact just got skipped over. Upon further investigation, a idiot started doing defragging on the target (destination) server without informing anybody in the enterprise and the previous days backup was running over 24+ hours instead of 2 hours. Sometime people cheat and try to enable/disable jobs and in those cases you may want to add notification if something like this happens. http://www.mssqltips.com/sqlservertip/1803/auto-alert-for-sql-agent-jobs-when-they-are-enabled-or-disabled/


    Sankar Reddy

    Blog: http://SankarReddy.com/
    Twitter: http://twitter.com/SankarReddy13/

    • Marked as answer by lostinbrisbane Wednesday, March 21, 2012 5:22 AM
    Monday, March 19, 2012 5:21 AM
    Moderator
  • Hi lostinbrisbane,

    There could be so many causes for this issue. Restarting the SQL Server Agent service always solve the issue, you can try it if you need to solve it as soon as possible.

    For troubleshooting this issue, please first check the permissions of your service account and job owner if their permission has been changed and then make sure the SQL Server Agent service, include jobs and schedules have the correct configuration. After checking, you can try to run the job manually see what happens. If it is running well, maybe you’d better try as Sankar mentioned above, there could be something block your job.


    Best Regards,
    Iric
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    • Marked as answer by lostinbrisbane Wednesday, March 21, 2012 5:22 AM
    Tuesday, March 20, 2012 2:38 AM
    Moderator
  • The key point here is there are not logs related to this miss at all.

    I have dropped the agent task and recreated on same server and restarted the Agent service. It did fix the problem by far but still I could not find out any reason why this happened. Backup issues may be one of them as we had SAN issues with that server.


    Wednesday, March 21, 2012 5:21 AM

All replies

  • Hi,

    Can you create a new job that runs something simple such as @@servername or similar and schedule it to run say 5-10 minutes into the future so you can see if that processes correctly? Is it possible the SQL agent crashed and was recovered (although you should see logs for this).


    Sean Massey | Consultant, iUNITE

    Feel free to contact me through My Blog, Twitter or Hire Me.
    Please click the Mark as Answer button if a post solves your problem!

    Monday, March 19, 2012 1:48 AM
  • Hi,

    Sometimes there are valid reasons a job will NOT kick-in on the scheduled time. Sometime ago, our database full backup job didn't start on time and in fact just got skipped over. Upon further investigation, a idiot started doing defragging on the target (destination) server without informing anybody in the enterprise and the previous days backup was running over 24+ hours instead of 2 hours. Sometime people cheat and try to enable/disable jobs and in those cases you may want to add notification if something like this happens. http://www.mssqltips.com/sqlservertip/1803/auto-alert-for-sql-agent-jobs-when-they-are-enabled-or-disabled/


    Sankar Reddy

    Blog: http://SankarReddy.com/
    Twitter: http://twitter.com/SankarReddy13/

    • Marked as answer by lostinbrisbane Wednesday, March 21, 2012 5:22 AM
    Monday, March 19, 2012 5:21 AM
    Moderator
  • Hi lostinbrisbane,

    There could be so many causes for this issue. Restarting the SQL Server Agent service always solve the issue, you can try it if you need to solve it as soon as possible.

    For troubleshooting this issue, please first check the permissions of your service account and job owner if their permission has been changed and then make sure the SQL Server Agent service, include jobs and schedules have the correct configuration. After checking, you can try to run the job manually see what happens. If it is running well, maybe you’d better try as Sankar mentioned above, there could be something block your job.


    Best Regards,
    Iric
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    • Marked as answer by lostinbrisbane Wednesday, March 21, 2012 5:22 AM
    Tuesday, March 20, 2012 2:38 AM
    Moderator
  • The key point here is there are not logs related to this miss at all.

    I have dropped the agent task and recreated on same server and restarted the Agent service. It did fix the problem by far but still I could not find out any reason why this happened. Backup issues may be one of them as we had SAN issues with that server.


    Wednesday, March 21, 2012 5:21 AM
  • have you change your server to a future date for testing?

    if you did, you might need to restart SQL server agent to make your job able to run again.

    Sunday, September 7, 2014 2:47 AM
  • Restart of the Agent Solved my problem.

    Thanks

    Sunday, September 11, 2016 7:35 PM
  • OLD thread!

    Regards, S_NO "_"

    Monday, September 12, 2016 12:27 AM