Differences

This shows you the differences between the selected revisions of the page.

2014-07-25 2014-07-25
typo (martin) recommending to use winscp.com when cheking console output (martin)
Line 13: Line 13:
If the task works correctly from Command prompt, see [[faq_scheduler|My script works fine when executed manually, but fails or hangs when run by Windows Scheduler, SSIS or other automation service. What am I doing wrong?]] If the task works correctly from Command prompt, see [[faq_scheduler|My script works fine when executed manually, but fails or hangs when run by Windows Scheduler, SSIS or other automation service. What am I doing wrong?]]
-If the task fails even when run from Command prompt, inspect an output of the task for any error. If you see an error, check list of [[messages|common error messages]] or search this website for the error.+If the task fails even when run from Command prompt, inspect a console output of the task for any error. If you see an error, check list of [[messages|common error messages]] or search this website for the error. To check for an error in console output, it is [[troubleshooting#scripting|recommended]] to use ''[[executables|winscp.com]]''.
If the problem is not obvious from the output, enable logging to a file as described below. If the problem is not obvious from the output, enable logging to a file as described below.

Last modified: by martin