Differences

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

troubleshooting 2020-09-16 troubleshooting 2024-09-25 (current)
Line 4: Line 4:
When facing an issue with WinSCP, following resources and hints may help you to resolve the issue yourself: When facing an issue with WinSCP, following resources and hints may help you to resolve the issue yourself:
  * Try to find solution in [[faq|F.A.Q]], in our numerous [[guides|guides]] or in this [[start|documentation]]. Use //Search// box on the top right.    * Try to find solution in [[faq|F.A.Q]], in our numerous [[guides|guides]] or in this [[start|documentation]]. Use //Search// box on the top right. 
-  * If you are getting an error message, the checklist of [[messages|common error messages]].+  * If you are getting an error message, check the list of [[messages|common error messages]].
  * Try to find a solution in tens of thousands answered questions on [[&forum/|WinSCP support forum]]. Again, use the //Search// box on the top right, but navigate to the forum before you do so. -- Alternatively, select //"Support forum"// in the search results.   * Try to find a solution in tens of thousands answered questions on [[&forum/|WinSCP support forum]]. Again, use the //Search// box on the top right, but navigate to the forum before you do so. -- Alternatively, select //"Support forum"// in the search results.
  * There are hundreds of [[https://stackoverflow.com/questions/tagged/winscp|WinSCP questions answered on Stack Overflow]] and [[https://superuser.com/questions/tagged/winscp|Super User]] sites.   * There are hundreds of [[https://stackoverflow.com/questions/tagged/winscp|WinSCP questions answered on Stack Overflow]] and [[https://superuser.com/questions/tagged/winscp|Super User]] sites.
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]].
-  * If you are getting an error message, a checklist of [[messages|common error messages]].+  * If you are getting an error message, check the list of [[messages|common error messages]].
  * 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.
Line 26: Line 26:
  * Read guide for [[guide_automation|automation/scripting]] and other [[guides#scripting|related guides]].   * Read guide for [[guide_automation|automation/scripting]] and other [[guides#scripting|related guides]].
  * 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, a checklist 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 ''[[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. +winscp.com /ini=nul /script=script.txt /log=script.log /loglevel=* 
-  * See also [[guide_debugging_scheduler|Debugging transfer task running in Windows Scheduler, SSIS, or another automation service]]. +</code>     
-  * 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 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 =====

Last modified: by 157.33.248.190