Data Integrator Schedule Job Does Not Start

My DI job does not start automatically, but it runs OK if I start it manually, can DI gurus out there please help? :roll_eyes:


Kting (BOB member since 2004-07-08)

I am facing the same problem??

Can anyone help me out on this??

Thanks
Gopal Swaminathan


sgopal_78 (BOB member since 2004-07-27)

I had exactly the same problem a few weeks ago. We had only the scheduler installed on our server, with Designer installed on a local pc. The scheduler would execute jobs without a hitch but would not run via a schedule.

The only way I could resolve it was to do a full installation on the server - i.e. including Designer - and subsequently all our jobs are running via schedules quite happily.

Not sure if this will help either of your situations but here’s hoping… :slight_smile:
Nik


EvilEye (BOB member since 2004-08-12)

The DI scheduler relies on an operating system scheduler (either AT on Windows, or CRON on Unix).

For Windows: are you sure the Scheduled Tasks service is running?

Also: There is a known issue where as part of the install, a required DI file “FLSTUBDLL.DLL” not getting installed; this is required to make the scheduling work. Contact BO support if you don’t see this file on your DI server.


dnewton :us: (BOB member since 2004-01-30)

Make sure you make the SCHEDULE active after scheduling the job in web admin.


Jkespel (BOB member since 2004-10-30)

Hi,

I have the same issue, The Scheduled Jobs show as Active within the Management Console, yet they still don’t run. Is this a Known error?

Is there anything I can try without doing a full re-install?

Thanks


wlloyd (BOB member since 2008-10-14)

No need to perform a re-install.

What I’ve seen is that the Windows scheduler sometimes loses the schedule. I’m not sure how this happens. I don’t believe that it is anything that someone is mistakenly deleting.

The easiest solution is to simply de-activate then re-activate the scheduled job from the DS Management Console.

You can check the scheduled items in Windows by typing AT from the command line. If you are logged in as an administrator then you should see everything.


eganjp :us: (BOB member since 2007-09-12)