SQL Server Agent jobs not running as scheduled

  • Jimmy M

    Default port

    Points: 1481

    Hi all, has anyone encountered sql server agent not actually running the jobs it is schdeduled to run?!

    It was recently brought to my attention that some daily jobs have not been running. When i looked in Job Activity Monitor, the jobs were showing a last run date of 1st April and a next run date of 2nd April. It shows the same again even now, and the job history confirms there have been no runs since 1st April.

    The jobs are enabled, their schedules are enabled and there is no end date set on the schedule. But sql server agent is showing a next run date in the past.

    It is seemingly ... "stuck". I can give it a push by running the job manually, at which point the job's schedule comes back to life and sql server agent runs the job again as per the schedule.

    In other words i can "fix" this issue by starting every job manually! I can also get all jobs running again by restarting sql server agent. But i am keen to know the underlying reason behind this.

    We are running sql server 2008 SP2 (10.0.4000) x64 Enterprise Edition, running on on a Windows 2008 R2 OS. We have 3 instances on an active-passive cluster, which is made up of 2 VMs.

    Please note: this behaviour is the same for all 3 sql instances running on this cluster (and the same VM). 1st April is the key date for all of the instances - the last jobs running just before midnight on 2nd April.

    There has not been a failover or, to my knowledge, a sql agent restart since mid February.

    Up to and for a few days after 1st April there were a number of very minor (less than 1 second) system time changes recorded in the system event log, including one at 23:56 on 1st April. So i am wondering if this is at the heart of the problem.

    Has anyone seen sql server agent behave in this way, i.e. not actually running pending jobs, and did you pin it down to anything, e.g. virtual machines, system time changes, sql clustering, a sql/OS version/patch?

    Many thanks

  • Grant Fritchey

    SSC Guru

    Points: 395579

    On this one, I'd get in touch with Microsoft. That sounds like you've run into something serious.

    ----------------------------------------------------
    The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood...
    Theodore Roosevelt

    The Scary DBA
    Author of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd Edition
    Product Evangelist for Red Gate Software

  • Ninja's_RGR'us

    SSC Guru

    Points: 294069

    I'll be listening on this thread... I've had that problem once on sql 2000 a couple years ago. I just manually restarted the schedule but I never understood why I had that problem.

  • Syed Jahanzaib Bin hassan

    SSChampion

    Points: 11410

    That is a serious issue,did you check to bounce the agent service,

    for the time being create an sp and include all jobs start script as

    sp_start_job 'test1'

    sp_start_job 'test2'

    and so on......

    and then create a batch file with SQLCMD and schedule it on OS level

    Regards,

    Syed Jahanzaib Bin Hassan

    MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA

    My Blog

    http://www.aureus-salah.com

    Regards,
    Syed Jahanzaib Bin Hassan
    BSCS | MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA

    My Blog
    www.aureus-salah.com

  • Ninja's_RGR'us

    SSC Guru

    Points: 294069

    Syed Jahanzaib Bin hassan (4/21/2011)


    That is a serious issue,did you check to bounce the agent service,

    for the time being create an sp and include all jobs start script as

    sp_start_job 'test1'

    sp_start_job 'test2'

    and so on......

    and then create a batch file with SQLCMD and schedule it on OS level

    Regards,

    Syed Jahanzaib Bin Hassan

    MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA

    My Blog

    http://www.aureus-salah.com[/quote%5D

    Wow talk about yet ANOTHER moronic post (see his last 5-10 posts). What about the consequence of running a job at the wrong time or taking production down because you just overloaded the server?

  • Syed Jahanzaib Bin hassan

    SSChampion

    Points: 11410

    Hey Ninja Turtle,you are again talking about non sense and stupid but why Ninja Turtle why

    I'll be listening on this thread... I've had that problem once on sql 2000 a couple years ago. I just manually restarted the schedule but I never understood why I had that problem.

    Wow talk about yet ANOTHER moronic post (see his last 5-10 posts). What about the consequence of running a job at the wrong time or taking production down because you just overloaded the server?

    you are here to provide solution,if you dont have answer then dont try to increase your points ,no body ask about your funny and non technical stories here

    Regards,

    Syed Jahanzaib Bin Hassan

    MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA

    My Blog

    http://www.aureus-salah.com

    Regards,
    Syed Jahanzaib Bin Hassan
    BSCS | MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA

    My Blog
    www.aureus-salah.com

  • Ninja's_RGR'us

    SSC Guru

    Points: 294069

    Syed Jahanzaib Bin hassan (4/23/2011)


    Hey Ninja Turtle,you are again talking about non sense and stupid but why Ninja Turtle why

    I'll be listening on this thread... I've had that problem once on sql 2000 a couple years ago. I just manually restarted the schedule but I never understood why I had that problem.

    Wow talk about yet ANOTHER moronic post (see his last 5-10 posts). What about the consequence of running a job at the wrong time or taking production down because you just overloaded the server?

    you are here to provide solution,if you dont have answer then dont try to increase your points ,no body ask about your funny and non technical stories here

    Regards,

    Syed Jahanzaib Bin Hassan

    MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA

    My Blog

    http://www.aureus-salah.com[/quote%5D

    Your solution has the potential to destroy a working environement depending on what jobs are in place and what they are doing. Your solution is to just run everything I'm pointing out the danger in that.

    If you can't understand that then I strongly recommend you change career.

  • Syed Jahanzaib Bin hassan

    SSChampion

    Points: 11410

    That solution for manual jobs execute automatically,It will check by the DBA which one is resource full and etc,I will not suggest you to change the career because I love challanges but I would like to add in the end just change your way of talking and attitude,that is unprofessional,be a professional ok

    Regards,

    Syed Jahanzaib Bin Hassan

    MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA

    My Blog

    http://www.aureus-salah.com

    Regards,
    Syed Jahanzaib Bin Hassan
    BSCS | MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA

    My Blog
    www.aureus-salah.com

  • Jimmy M

    Default port

    Points: 1481

    Just to say that I did indeed restart sql server agent (tecnically speaking, as it is a cluster i took the sql server agent resource offline and brought it online again). This worked - that is to say sql server agent did starting running jobs again as per the schedules. As i mentioned in the original post i was also able to get an individual job running on its schedule again by running the job manually, seemingly bringing the job or its schedule back to life in some way!

    Anyway, as it's a non-production system the feeling here is that i put this one to bed and keep an eye on this cluster and the others on the same virtual machine host. If i ever see this again i shall log a call with MS.

    Cheers all.

  • Eric Zierdt

    Ten Centuries

    Points: 1333

    Just saw this thread, I've encountered this problem on my staging server (not clustered) and today on my production server (clustered). For the record, both servers are 2008 R2. It seems that this happens after I restart the services (or take offline/bring online on the cluster), the SQL Server Agent service appears to be online, says it's online and if I close and re-open the Job Activity Monitor it opens fine and shows my jobs are enabled and ready to run, but the time passes and the jobs don't start.

    I'm interested if anyone with this issue found a solution. Restarting the Agent Service usually does get things rolling.

  • JPac

    SSC Journeyman

    Points: 99

    I'm bumping this thread because i too am seeing this issue on one of our Dev Servers with a number of Instances installed (Mixed 2005 and 2008 R2). However after running the job manually and successfully, and restarting the Agent, the scheduled jobs are still not running. I am going to bounce this box later today to see if that can fix the issue. Anyone else have any fixes for this???

  • JPac

    SSC Journeyman

    Points: 99

    i rebooted the server, and this issue still remains. I am going to patch all 2008 R2 instances to the latest CU. and hope that fixes the issue. I should note, that only the 2008 R2 instances are having Agent issues, the 2005 instances do not seem to be affected by this issue.

  • vultar

    Hall of Fame

    Points: 3260

    I've seen this before on a non-prod cluster and restarting the agent also fixed the problem.

    For me, me the problem appeared after the system clock was maunally changed.

    Cheers

    Vultar

  • rstone

    SSCertifiable

    Points: 6011

    On one of our servers, we are having an issue reaching a DC during reboots. I notice that the agent can still start, however, none of the "next run" dates are populated. No jobs get run at all.

    If I restart the agent, the "next run" dates get populated.

    Other services (e.g., SSAS and SSRS) fail to start during the reboot, but start manually after the reboot.

    Perhaps the issue is the same and related to a NETLOGON 5719 error.

    Randy
    Helpdesk: Perhaps Im not the only one that does not know what you are doing. 😉

  • Resender

    SSCertifiable

    Points: 7285

    I hate raising threads from the dead but I got the same issue on an SQL Server 2008 R2.

    last week I was asked to reschedule a daily job from 8:30 AM mon-fri to 9:30 AM each day.

    Now the job no longer runs each day & manually starting the job doesn't seem to kickstart the schedule.

Viewing 15 posts - 1 through 15 (of 28 total)

You must be logged in to reply to this topic. Login to reply