Differences
This shows you the differences between the selected revisions of the page.
| troubleshooting 2020-10-03 | troubleshooting 2024-09-25 (current) | ||
| Line 16: | Line 16: | ||
| * Read guide for [[guide_connect|connecting to FTP/SFTP server]]. | * Read guide for [[guide_connect|connecting to FTP/SFTP server]]. | ||
| * Try if you can connect with other clients using the same protocol. | * Try if you can connect with other clients using the same protocol. | ||
| - | * If you can connect with another client, check [[faq_connection_refused|why WinSCP may not be able to connect to a server when other clients are]]. | + | * If you can connect with another client, see [[faq_connection_refused|*]]. |
| * When using SFTP/SCP, it may be useful to try to connect with an SSH terminal client (such as [[&url(putty)|PuTTY]]). You may get some useful messages back on the terminal screen. | * When using SFTP/SCP, it may be useful to try to connect with an SSH terminal client (such as [[&url(putty)|PuTTY]]). You may get some useful messages back on the terminal screen. | ||
| * Check other [[faq#connecting|F.A.Q. on connection]]. | * Check other [[faq#connecting|F.A.Q. on connection]]. | ||
| 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. \\ <code batch> | ||
| + | winscp.com /ini=nul /script=script.txt /log=script.log /loglevel=* | ||
| + | </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|*]] | ||
| ===== [[timestamps]] Troubleshooting Timestamp Issues ===== | ===== [[timestamps]] Troubleshooting Timestamp Issues ===== | ||