Differences
This shows you the differences between the selected revisions of the page.
| 2020-12-25 | 2023-01-20 (current) | ||
| syntax (martin) | I've forgot about this article, so merging all info from intended guide_debugging_script (to be deleted now) (martin) | ||
| Line 27: | Line 27: | ||
| * Check [[faq#scripting|F.A.Q. on scripting/automation]]. | * Check [[faq#scripting|F.A.Q. on scripting/automation]]. | ||
| * If you are getting an error message, check the list of [[messages|common error messages]]. | * If you are getting an error message, check the list of [[messages|common error messages]]. | ||
| - | * Turn on [[logging|session logging]] using [[commandline#logging|''/log'' command-line switch]] and check the generated log file to see, if WinSCP actually does what you want it to do. IF you are having problems with password authentication, enable password logging using [[commandline#logging|''/loglevel=*'' command-line switch]] and check the log, if a correct password is being used. | + | * Turn on [[logging|session logging]] using [[commandline#logging|''/log'' command-line switch]] and check the generated log file to see, if WinSCP actually does what you want it to do. If you are having problems with password authentication, enable password logging using [[commandline#logging|''/loglevel=*'' command-line switch]] and check the log, if a correct password is being used. \\ <code batch> |
| - | * If no session log is created, chances are that some error prevented WinSCP from starting, creating a log, or starting a session. Check WinSCP console output for any error. It is recommended to execute ''[[executables|winscp.com]]'' from existing console window (such as from Windows ''cmd.exe''). The ''winscp.com'' inherits the console((A ''winscp.exe'' always creates a new console that closes when WinSCP finishes.)) and when it exits with an error, the error is preserved on the console, allowing you to inspect it. | + | winscp.com /ini=nul /script=script.txt /log=script.log /loglevel=* |
| - | * See also [[guide_debugging_scheduler|*]]. | + | </code> |
| + | * If no session log is created, chances are that some error prevented WinSCP from starting, creating a log, or starting a session. Check WinSCP console output for any error. It is recommended to execute ''[[executables|winscp.com]]'' from an existing console window (such as from Windows Command Prompt – ''cmd.exe'' or PowerShell). \\ &screenshotpict(scripting_debugging) \\ The ''winscp.com'' inherits the console((A ''winscp.exe'' always creates a new console that closes when WinSCP finishes.)) and when it exits with an error, the error is preserved on the console, allowing you to inspect it. | ||
| + | * See also [[guide_debugging_scheduler|*]] or \\ [[faq_batch_file|*]] | ||
| * If you cannot log in or transfer the file using a script, yet you can log in or transfer the file in GUI, see [[faq_script_vs_gui|*]] | * If you cannot log in or transfer the file using a script, yet you can log in or transfer the file in GUI, see [[faq_script_vs_gui|*]] | ||