Video Screencast Help

Jobs Not Starting when scheduled from axsched.exe or mm_schedule_event

Created: 31 Jan 2014 | 1 comment

When a job is scheduled from axsched.exe or mm_schedule_event stored procedure it doesn't kick off based on the schedule. Whether the schedule is in the past or in the future. The job is created but the status is blank. I have to refresh the console in order for it to start. Our application and database are separated, so it's almost like some type of trigger isn't happening. Has anyone seen this?

DS 6.9 SP6

Comments 1 CommentJump to latest comment

ianatkin's picture

We're *not* seeing this here. ImageInvoker uses axsched.exe behind the scenes and this has carried on working fine for us through the upgrade to SP6.

But I have seen this in the past. When I was developing ImageInvoker I tried to bypass the use of axsched.exe and create the job schedules in T-SQL myself. When I did that, I found that the jobs never kicked off by themselves.. only a console refresh seemed to do the trick.

When I went back to using axsched.exe, this problem disappeared.

My ultimate resolution to speed up job scheduling was to use axsched.exe to schedule the *first* job only, and then use T-SQL directly for the rest. This combination gave me most of the scheduling speed I wanted whilst avoiding the problem of requiring a console refresh to trigger some action....

So... try deleting the computer object in case you've done anything horrible to it, and try axched.exe again and see what happens?

Ian Atkin, IT Services, Oxford University, UK

Connect Etiquette: "Mark as Solution" those posts which assist you most in resolving your problem, and give a thumbs up to useful articles and downloads