Differences

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

2014-06-03		2014-07-25
Restored revision 1398431687. Undoing revisions 1401771428, 1401771466. (martin) (hidden)		console output inspection (martin)
	Line 27:		Line 27:
	* If you are getting an error message, check list of [[messages\|common error messages]].		* If you are getting an error message, check list of [[messages\|common error messages]].
	* Turn on [[logging\|session logging]] and check the generated log file to see if WinSCP actually does what you want it to do.		* Turn on [[logging\|session logging]] and check the generated log file to see if WinSCP actually does what you want it to do.
		+	* 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 other automation service]].		* See also [[guide_debugging_scheduler\|Debugging transfer task running in Windows Scheduler, SSIS or other automation service]].

2014-06-03		2014-07-25
Restored revision 1398431687. Undoing revisions 1401771428, 1401771466. (martin) (hidden)		console output inspection (martin)
	Line 27:		Line 27:
	* If you are getting an error message, check list of [[messages\|common error messages]].		* If you are getting an error message, check list of [[messages\|common error messages]].
	* Turn on [[logging\|session logging]] and check the generated log file to see if WinSCP actually does what you want it to do.		* Turn on [[logging\|session logging]] and check the generated log file to see if WinSCP actually does what you want it to do.
		+	* 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 other automation service]].		* See also [[guide_debugging_scheduler\|Debugging transfer task running in Windows Scheduler, SSIS or other automation service]].

Documentation