Windows Task Scheduler fails to run a batch file with an OE1

Posted by MBeynon on 24-Sep-2019 08:48

Hi,

We have a number of  Windows Tasks scheduled to run at vatious times of the day. They each call the same batch file and pass in a parameter which determines some action to take within the called program;

C:\oe116\bin\prowin32.exe -basekey ini -ininame my.ini -pf runTasks.pf -b -p RunTasks.r -param '%1'> null

All the Tasks bar one run as expected at their alloted times. However, 1 task trys to run and then returns immediately with a code of 102

With the exception of the run times and the parameter passed in the the batch file the tasks are identical.

Searching through the KB one suggestion is to delete and recreate the Task. I've tried this but to no avail.

We are running OE11.6 on a 64bit Standard Windows Server 2019.

Any, help would e greatly appreciated.

Thanks

All Replies

Posted by Matt Gilarde on 24-Sep-2019 11:52

Have you tried using _progres.exe instead of prowin32.exe?

Posted by frank.meulblok on 24-Sep-2019 11:58

The obvious things to check:

- What's the exact command line being executed, including the parameter substitutions performed in the batch file ?

- What happens if that exact command line is run from a command prompt instead of from the Scheduled Task ? Does the job run normally then or not ? (Do make sure to use the same user account etc. as well) ?

Less obvious:

- What happens if you use _progres.exe instead of prowin32.exe to run the jobs ?

The GUI client executable can have some bizarre and unwanted side effects that the character client doesn't suffer from. And using the character client executable instead should not mean loss of functionality, since something designed as Scheduled Task should not have any UI interaction anyway.

Posted by James Palmer on 24-Sep-2019 12:01

Is there any chance of implementing Jenkins? It tends to be more robust than the Windows Task Scheduler and has a lot more options. There's also the added benefits of out of the box error reporting.

Posted by Roger Blanchard on 24-Sep-2019 12:54

>>And using the character client executable instead should not mean loss of functionality, since something designed as Scheduled Task should not have any UI interaction anyway.

Unless of course you want UI such as a notify icon. If you have a running process such as a DB sync manager or a JMS client sending messages you may want to alert with errors. A notify icon is great for that.

This thread is closed