Differences

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

2020-10-05 2020-12-23
Restored revision 1600254137. Undoing revision 1601720492. (martin) (hidden) normalizing link (martin)
Line 28: Line 28:
  * 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.
-  * 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 ''[[executable|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.+  * 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.
  * See also [[guide_debugging_scheduler|Debugging transfer task running in Windows Scheduler, SSIS, or another automation service]].   * See also [[guide_debugging_scheduler|Debugging transfer task running in Windows Scheduler, SSIS, or another automation service]].
  * 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|Why I cannot connect/transfer using script, when I can using 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|Why I cannot connect/transfer using script, when I can using GUI?]]

Last modified: by martin