Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

SQL Server Agent jobs not running as scheduled Expand / Collapse
Author
Message
Posted Wednesday, June 20, 2012 2:03 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, September 10, 2014 9:48 AM
Points: 2, Visits: 239
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???
Post #1318965
Posted Wednesday, June 20, 2012 8:37 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, September 10, 2014 9:48 AM
Points: 2, Visits: 239
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.
Post #1319059
Posted Thursday, June 21, 2012 3:59 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, September 9, 2014 2:14 AM
Points: 234, Visits: 1,094
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
Post #1319188
Posted Monday, February 4, 2013 1:34 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Yesterday @ 5:34 PM
Points: 373, Visits: 611
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
"Perhaps I'm not the only one that does not know what you are doing."
Post #1415481
Posted Tuesday, April 8, 2014 2:04 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Yesterday @ 8:32 AM
Points: 338, Visits: 971
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.
Post #1559395
Posted Wednesday, April 9, 2014 6:39 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Yesterday @ 5:34 PM
Points: 373, Visits: 611
Have you tried restarting the agent? That is what seems to be required to get it working again in some cases.

Randy
"Perhaps I'm not the only one that does not know what you are doing."
Post #1560219
Posted Monday, August 18, 2014 8:49 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Yesterday @ 9:37 AM
Points: 64, Visits: 448
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.
Post #1604489
Posted Monday, August 18, 2014 10:42 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Yesterday @ 5:34 PM
Points: 373, Visits: 611
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
"Perhaps I'm not the only one that does not know what you are doing."
Post #1604562
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse