Differences
This shows you the differences between the selected revisions of the page.
| 2018-02-01 | 2020-03-03 | ||
| Inspecting Output Log (martin) | missing verb (martin) | ||
| Line 37: | Line 37: | ||
| If a session log file is not even created, when executed from Windows Scheduler/%%SSIS%%, although the same WinSCP command and logging is working, when executed manually on command-line, there can be some problem in the Windows Scheduler/%%SSIS%% environment that prevents WinSCP from starting or writing to the log. | If a session log file is not even created, when executed from Windows Scheduler/%%SSIS%%, although the same WinSCP command and logging is working, when executed manually on command-line, there can be some problem in the Windows Scheduler/%%SSIS%% environment that prevents WinSCP from starting or writing to the log. | ||
| - | To debug such problems, wrap WinSCP command to a batch file and redirect WinSCP console output to a file. Make sure you use a console interface tool ''[[executables|winscp.com]]'', instead of ''winscp.exe''. It also useful to log something to the output file before running WinSCP, to verify that output logging is working. | + | To debug such problems, wrap WinSCP command to a batch file and redirect WinSCP console output to a file. Make sure you use a console interface tool ''[[executables|winscp.com]]'', instead of ''winscp.exe''. It is also useful to log something to the output file before running WinSCP, to verify that output logging is working. |
| The batch file can look like: | The batch file can look like: | ||