Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL Server Agent jobs not running as scheduled


SQL Server Agent jobs not running as scheduled

Author
Message
JPac
JPac
Forum Newbie
Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: General Forum Members
Points: 3 Visits: 298
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
JPac
Forum Newbie
Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: General Forum Members
Points: 3 Visits: 298
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
vultar
Old Hand
Old Hand (310 reputation)Old Hand (310 reputation)Old Hand (310 reputation)Old Hand (310 reputation)Old Hand (310 reputation)Old Hand (310 reputation)Old Hand (310 reputation)Old Hand (310 reputation)

Group: General Forum Members
Points: 310 Visits: 1213
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
rstone
SSC-Addicted
SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)

Group: General Forum Members
Points: 405 Visits: 824
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 I'm not the only one that does not know what you are doing." ;-)
Resender
Resender
SSC-Addicted
SSC-Addicted (473 reputation)SSC-Addicted (473 reputation)SSC-Addicted (473 reputation)SSC-Addicted (473 reputation)SSC-Addicted (473 reputation)SSC-Addicted (473 reputation)SSC-Addicted (473 reputation)SSC-Addicted (473 reputation)

Group: General Forum Members
Points: 473 Visits: 1564
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.
rstone
rstone
SSC-Addicted
SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)

Group: General Forum Members
Points: 405 Visits: 824
Have you tried restarting the agent? That is what seems to be required to get it working again in some cases.

Randy
Helpdesk: "Perhaps I'm not the only one that does not know what you are doing." ;-)
drewbengals
drewbengals
Valued Member
Valued Member (64 reputation)Valued Member (64 reputation)Valued Member (64 reputation)Valued Member (64 reputation)Valued Member (64 reputation)Valued Member (64 reputation)Valued Member (64 reputation)Valued Member (64 reputation)

Group: General Forum Members
Points: 64 Visits: 515
I had issues where a job seemingly stopped working even though it showed enabled and scheduled. I was able to track it back to a line of TSQL that was re-enabling the job if it was disabled. We have a notification job that is sending messages but when someone was working on areas that would cause notifications they would manually disable this job while it was being worked on. So we have a second job that was a "fail safe" that would check if the original job had been disabled for more than 30 minutes and if so it would re-enable it, but the problem was that it re-enabled it via an UPDATE to the sys.jobs table directly instead of using sp_update_job. Once we switched that command it solved the issue.
rstone
rstone
SSC-Addicted
SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)SSC-Addicted (405 reputation)

Group: General Forum Members
Points: 405 Visits: 824
That would explain it. The agent job information cached has to be refreshed. This is not done when using system tables directly. In addition, the supported methods help insure replication and multi-server job changes are handled correctly.

Randy
Helpdesk: "Perhaps I'm not the only one that does not know what you are doing." ;-)
bc6hix
bc6hix
Forum Newbie
Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)Forum Newbie (7 reputation)

Group: General Forum Members
Points: 7 Visits: 35
For what it is worth, I just ran into the issue of what I thought an Agent job not running as scheduled. It turned out that the job never finished from day before. Sometimes the easy answer is the one worth checking first.
MI_DBA
MI_DBA
Grasshopper
Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)

Group: General Forum Members
Points: 16 Visits: 84
once I faced a similar issue, turned out server was patched and after reboot, system date time settings were screwed and system itself was showing past date. Hence sql server agent was showing past date in 'next run' field

check what timw your sql server is showing select getdate()
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search