Differences

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

2020-09-16 2020-10-03
misunderstanding (martin) no summary (109.90.82.254) (hidden) (untrusted)
Line 22: Line 22:
  * If the server refuses to accept your connection or drops the connection suddenly, you should better check the server (e.g. its log file) first to find out the reason. Contact the server administrator if you cannot check the server yourself.   * If the server refuses to accept your connection or drops the connection suddenly, you should better check the server (e.g. its log file) first to find out the reason. Contact the server administrator if you cannot check the server yourself.
-===== [[scripting]] Troubleshooting Scripting/Automation Issues ===== +
-When you are facing issue with [[scripting|scripting/automation]]: +
-  * Read guide for [[guide_automation|automation/scripting]] and other [[guides#scripting|related guides]]. +
-  * Check [[faq#scripting|F.A.Q. on scripting/automation]]. +
-  * 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. +
-  * 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. +
-  * 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?]]+
===== [[timestamps]] Troubleshooting Timestamp Issues ===== ===== [[timestamps]] Troubleshooting Timestamp Issues =====

Last modified: by 109.90.82.254