Post a reply

Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)


Topic review


Thanks for your help!

I am ok with the setup now and it's working

But the log file getting big - is it only for debugging purpose and we should remove it in production environment? /console /log=inspection.log /passive=on /script=transferscript.txt

Is it a workaround for this /log=inspection.log? We still want to keep a log file in case it stops working and we know what it is


Re: keep alive

Please attach a full log file showing the problem (using the latest version of WinSCP).

To generate log file, use /log=path_to_log_file command-line argument. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.

keep alive


I try to use script to automate file transfer to hosted server, but it always get disconnected and reconnected all the times.

But if I use GUI, then the transfer is completed successfully

I check the log file and it shows below

2016-03-31 09:44:37.411 Session upkeep
2016-03-31 09:44:37.411 Sending dummy command to keep session alive.

Would you know how I can do that in scripting?

I would attached here

1/ my batch and scripting file for transferring (transfer got disconnected)

2/ log file for GUI transfer (completed transfer)

Thanks all for helping!