Job schedule will not remain enabled

Question

Job schedule will not remain enabled

Elliott Berkihiser

SSCarpal Tunnel

Points: 4068
More actions
December 12, 2005 at 1:08 pm

#115635

Hello everyone,
Sometimes newly created Jobs work fine, but do not re-start the next day. Usually, this is just a minor annoyance; I go in and "enable" and "apply" the Job Schedule and then the Job is good forever.
Now, however, I have a Job that was created by asking the DTS Designer to schedule a (new) package. This Job runs fine during the day, but will not re-start the next day. The Job Properties show the Job and the Schedule as "enabled", but the next day the Schedule is no longer marked "Enabled".
TIA,
Elliott

Viewing 14 posts - 1 through 13 (of 13 total)

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

Papillon Hall of Fame Points: 3303 More actions · Answer 1

Hi..

May be check the property for SQL Server Agent wheather it is checked for Autostart..u find that in SQL Server Property>>>Right Click

Regards,

Papillon

Jim C-203340 SSCommitted Points: 1716 More actions · Answer 2

What is the schedule of your package set for? (how often, what days, etc.)

Regards, Jim C

Andy Warren SSC Guru Points: 119902 More actions · Answer 3

Any chance you have another job/process disabling it?

Andy
SQLAndy - My Blog!
Connect with me on LinkedIn
Follow me on Twitter

Elliott Berkihiser SSCarpal Tunnel Points: 4068 More actions · Answer 4

Thanks for the suggestions. I don't know that any of them apply.

SQL Agent is already running (and running other jobs). The Job in question runs every minute from 4 am to 11pm (looking for an incoming FTP file). It runs fine when manually started. There are no interferences that I can see, but the schedule doesn't remain "enabled" overnight.

Jim C-203340 SSCommitted Points: 1716 More actions · Answer 5

Do you have an end date set on the schedule?

Regards, Jim C

Elliott Berkihiser SSCarpal Tunnel Points: 4068 More actions · Answer 6

No end date. The job should run M-F every minute from 4:00 am to 11:00 pm.

Roger Lindsay Ten Centuries Points: 1212 More actions · Answer 7

Don'y know what version or SP you are running, but this may be worth a look.

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q295378

Elliott Berkihiser SSCarpal Tunnel Points: 4068 More actions · Answer 8

lindr, thanks.

I didn't know about the SqlAgent.out file. I will look there for clues.

Elliott

Rudyx - the Doctor SSC-Forever Points: 43695 More actions · Answer 9

Another thought is to script out the JOB, delete it then add it back. I've had this happen once or twice and that did the trick.

RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

Elliott Berkihiser SSCarpal Tunnel Points: 4068 More actions · Answer 10

Thanks Rudy. The job just "died" again, and although I'm getting clues, it's still a mystery. I checked the SQLAgentOut log and sure enough there were messages involving "date calculation spin". Someone had mentioned this as a possible problem, but it was supposed to be fixed with the Service Pack 1. (We have sp3a).

I built a new job that should take over tomorrow morning. We'll see if starting fresh gets around the problem. Meanwhile I'm just bothered by something that should work and doesn't!

Roger Lindsay Ten Centuries Points: 1212 More actions · Answer 11

Elliot. I have only heard of this happening once before and scripting the job didn't work. Have you tried the workaround of creating multiple schedules, one for each day yet?

Elliott Berkihiser SSCarpal Tunnel Points: 4068 More actions · Answer 12

I'm aware of the workaround of building a job for each day of the week to avoid "date calculation spin", but I'm taking one more stab at doing it with one job. I wrote a new job from scratch and let it start this morning after the original job went dark last night.

I'll let you know next week if the clean version performs. Then, it's back to the work-around.

Elliott

Elliott Berkihiser SSCarpal Tunnel Points: 4068 More actions · Answer 13

Rebuilding the job from scratch solved the scheduling problem. Thanks to everyone for the suggestions.

Apparently there was a "date calculation spin" problem, but the easiest thing to do was simply paste the DTS job number into a freshly created job and go from there.

Elliott