g24ftp wrote:

To workaround this problem, we have to use an "ls" right after the "put" command. To me it seems, that the connection is closed "too early", causing the transfer to fail in Axway Synchrony Gateway. So the issue is still existing, maybe there was no relation to https://winscp.net/tracker/489 ?

Is it possible to sent some details to you? Are you interested?

Please start a new thread and attach a complete session log file.

Hi Martin,
I've just had an issue with Axway Synchrony Gateway and latest WinSCP 5.5.4. When we upload a file (FTPS) using winscp.com with a batch script, the file is received in the state "Interrupted" on Axway Synchrony Gateway.

To workaround this problem, we have to use an "ls" right after the "put" command. To me it seems, that the connection is closed "too early", causing the transfer to fail in Axway Synchrony Gateway. So the issue is still existing, maybe there was no relation to https://winscp.net/tracker/489 ?

Is it possible to sent some details to you? Are you interested?

Regards,
Tilo

This issue is being tracked already.

martin wrote:

Yes, please send me the details.

You will find my address (if you log in) in my forum profile.

Sent via E-Mail to you...

Yes, please send me the details.

Hi Martin,
we are running a Axway Synchrony Gateway at our site. Some of our customers have have issues when they try to upload a 0 byte file using FTPS and WinSCP. The transfers gets interrupted, which means in Synchrony Gateway that it has not completed successfully.
We have already opened a support request at Axway. The support people have looked at the issue. They have compared curl with WinSCP and have found out, that WinSCP closes the data connection too early causing an incomplete transfer in Synchrony Gateway.

Are you interested in the details of that problem? I have it available as a PDF document.

Thanks and regards,
Tilo