Troubleshooting Automation script tasks or jobs that do not run when scheduled. (4296144)

Automation script is not running when scheduled.  Either the job does not run at all or it does run, but there are no expected results.  If manually running the automation script in Toad, it will run fine and produce the expected results. The Windows Task Scheduler item can also look like it is hanged or frozen.

Please check the suggestions below:

RESOLUTION 1:
Ensure that you have the "Saved Password" option checked in the Connection Properties for the specified connection. Passwords need to be saved so that the application has the credentials to access the database. 

RESOLUTION 2:
If running on Windows 7, try disabling the Windows UAC (User Account control). Depending on user settings, if a prompt is displayed when accessing Toad, this could interrupt and hold up the automated job, preventing it from running and/or finishing. 

RESOLUTION 3:
In the Windows Task Scheduler Properties screen for the task/job item, make sure the "Run only if logged on" setting is not selected.  Ensure the "Run whether user is logged on or not" is the one selected.  Also check-mark the "Run with highest privileges" box.

RESOLUTION 4:
Verify that the computer / laptop that the jobs are scheduled to run on stays on (Note: specific users can be locked or logged off). If the computer is shut down, the task will not run. 

RESOLUTION 5:

Are there two different users that are being used? One to test run the Automation scripts and another to schedule the tasks? If so, check if the Windows user that is being used to run a scheduled task has the connection defined.  You can do this by launching TDP specifically under the Windows user in question, using the extended right-click context menu.

Note: Logging in as i.e. user_a and running programs via right-click | 'Run Using a Different User' and using another user i.e. user_b qualifies as two users involved even though a single machine is being used. 

1. Go to Start | Programs | TDP 3.X in the Start menu.
2. Press Shift then do right-click on the TDP 3.X short cut.
3. Right-click and choose ‘Run as different user.’
4. In the Windows Security dialog type in the Windows user in question and this user's password.
5. Press OK to launch TDP.
6. Do you see connections that are needed for your Automation script execution in the Connection Manager window? If not, please define them in the Toad Connection Manger. Don't forget to check mark the "Save Password" box.

Note: If the above suggestion doesn't work, for more advanced troubleshooting, please check the location of the Automation log files. By default, the files are located here:

Windows 7 - C:\Users\<user>\AppData\Roaming\Quest Software\Toad Data Point 3.x\Automation
Windows XP - C:\Documents and Settings\<your_user>Application Data\Quest Software\Toad Data Point 3.x\Automation

RESOLUTION 6:
If the Automation scheduling is being done on one PC (i.e. client), and the job or task is being run on another PC (i.e. server), try installing TDP and TIC on the server instead, and create the Automation script and scheduling again.  Basically, if possible, try to have TDP, TIC, and the database be all on the same computer.