ADO Dataset Iterator hangs when called via Task Scheduler?

Automise Discussion
1

I have gotten good answers from here so far, so here is another issue I have run into:

I have an Automise project that calls the ADO Iterator.  If I run the project within Automise, it runs fine.  If I run it from a command line using ATCMD, it runs fine.  If I run the same command line from the Task Scheduler after using the scheduler to create the task, it seems that the project hangs on the ADO Iterator step.  The iterator, at the moment, should return 0 rows and move to the next step in the project.  However, when I run the scheduled task, the task is still running after 20 minutes (from a command line, the whole project ends successfully in 3 seconds), and a look at the log seems to indicate that the ADO Iterator step starts but does not finish.  I have to end the scheduled task and THEN kill the ATCMD process in Task Manager to get it to stop.

The iterator itself is set up with the correct login/pwd to hit the database (as evidenced by other runs), and the login that is set up to run the scheduled task has permissions to run ATCMD.exe.  Are there special permissions within the ADO Iterator or project setup that are needed to make the ADO Iterator run from within a scheduled task?

Thanks,

Jonathan

2

OK, I have figured out that it is not the ADO Dataset Iterator. It is the program I am calling AFTER the ADO Dataset Iterator. I will start a new thread on that, and this one can be deleted.

3

Hi Jonathan,

Apologies for not seeing this post earlier. I will take a look at your new post.