July 27, 2007 at 7:23 am
I am having a strang e problem in Sql 2005 Enterprise RTM with the job scheduler.
Whenever I make a change to my schedule (enable or disable schedule, change frequency, time etc), the next run date and next run time (in sysjobschedules) does not get updated. Because of this, my job does not run every time I make a change to my schedule.
I am not sure, when SQL Server 2005 updates the job schedule. Can anyone throw some light on this. Is this a bug? What is the fix?
Give me a fish, you feed me for a day! Teach me to fish, you feed me for a life time.
July 27, 2007 at 8:44 am
Sysjobschedules refreshes every 20 minutes.
Are schedules enabled after you make the changes?
Is SQL Agent running?
July 27, 2007 at 8:55 am
Schedule was changed yesterday. The next run date and next run time is not updated till now. SQL Agent is running. Where is the setting (20 minutes) for sysjobschedule refresh? Thanks.
Give me a fish, you feed me for a day! Teach me to fish, you feed me for a life time.
July 27, 2007 at 9:04 am
You can't change this setting (http://msdn2.microsoft.com/en-us/library/ms188924.aspx)
Is this job enabled when you query sysjobs table in msdb?
What's the purpose of this job?
Did Sql Agent service account changed? like a new password?
July 27, 2007 at 9:31 am
Job is enabled and Schedule is enabled.
SQL Agent service account or password is not changed. Nothing is changed.
The job is to run SSIS package. Thanks.
Give me a fish, you feed me for a day! Teach me to fish, you feed me for a life time.
July 27, 2007 at 11:59 am
Right click on SQL Agent ---->Properties in the general tab check the "Include execution trace messages"
This will drill down to what's causing the errror.
Create a new job to execute the SSIS package but do not create schedules and execute it by right clicking the job and selecting "start job at step".
If the job doesn't run.
Check SQL Agent Error log and paste it here if you can.
Use this KB as a troubleshooting guide
http://support.microsoft.com/kb/918760
July 27, 2007 at 12:27 pm
The job runs fine if I start it manually. It is just that the schedule does not trigger the job if you change the schedule say from 11:00AM to 11:05AM.
BTW, "Include execution trace message" is checked. There are no error message as the job did not start at 11:05AM even though both job and schedule is enabled. The schedule time and frequency is set correct.
Give me a fish, you feed me for a day! Teach me to fish, you feed me for a life time.
July 27, 2007 at 12:37 pm
Justin how about this.
Change the schedule of the job from 11:00AM to 11:30AM.
July 27, 2007 at 12:47 pm
I tried changing the schedule several times and it is not updating sysjobschedules. I created a new schedule (keeping the original in place) for the same job. Sysjobschedules show 0 for both next run date and next run time (for the new schedule). Any more ideas!!!
Give me a fish, you feed me for a day! Teach me to fish, you feed me for a life time.
July 27, 2007 at 12:59 pm
The Sysjobschedules will always show 0 until it gets refreshed.
Check the Jobs Activity Monitor and you will see Next Run Time is filled.
July 27, 2007 at 1:12 pm
one minute after I added new schedule, it set the next run date and next run time correct for both schedules. But, still I do not understand why it does not refresh next run date and next run time every time there is a change in schedule. Thanks.
Give me a fish, you feed me for a day! Teach me to fish, you feed me for a life time.
July 28, 2007 at 12:06 am
your sql server agent is in hanged state so just restart your sql server agent service all will be fine i guess......thanks
[font="Verdana"]- Deepak[/font]
August 7, 2015 at 8:31 am
delete the schedule and re-create, it will work.
August 7, 2015 at 9:05 am
biswal.swapna.samjit (8/7/2015)
delete the schedule and re-create, it will work.
You do know that you are responding to an 8 year old thread.
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply