Greetings! I have a project that goes and gets some data via the ADO Iterator, and puts the data into one of two files. The project then runs Open Air Integration Manager using Execute Program. It runs the IM twice - once for each of the data files.
When I run the project from the Automize IDE, it runs fine. When I run from the command line using ATCMD, it runs fine.
When I run the project as a Scheduled Task, the project gets to the end of the ADO Iterator piece, and then hangs. It is difficult to tell whether it actually starts up the Integration Manager - I know that it completes the ADO Iterator, and the first run of the OA IM is the next thing to be run as part of the project.
Is there something special I need to do when calling an Execute Program from within a project that is being scheduled using Task Scheduler? Do programs tend to not return control to the project?
Thank you for any help - I have been battling this all day, and I am not sure where to go from here.
Thanks,
Jonathan
Hi Jonathan,
The typical things to look at when scheduling a task are as follows;
- The permissions of the user running the task are sufficient for running and accessing all locations required by the script.
- If the scheduler is allowed to run even when no one is logged in, then make sure no GUI application is run from the script. Windows has a limitation of running scheduled tasks which require a GUI.
- No mapped drives are used, or network locations are used by the script or in the scheduler. There are ways around this, but it tends to complicate the script and errors which occurs.
Further to all the above if you could provide some more details about what Open Air Integration Manager is and what the command line parameters being used are. This will allow me to understand more fully what is occurring in the script, and therefore what could be stopping the scheduler from working.
Actually, it was related to permissions. The user that the script was running under had implicit permissions to modify the directories and files that it needed to, but apparently I had to specify explicit permissions for that user. As all of my other testing was under my ID, I was not aware of the issue until I logged onto the box using the ID that the scheduled task was running under and found that I could not run the OA IM application fully.
This is not an Automise issue - sorry to bring it here.
Thanks,
Jonathan
Hi Jonathan,
Great to hear you got it solved. Sadly on Windows permission issues are very hard to diagnose at times. As you have found, testing the feature that is failing with the same permissions as your running service tends to bring to light what is occurring under the skin.
Also always more than happy to help.