Post a reply

Options
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)

Options

Topic review

KevinV

Okay, I will work on putting that together. This doesn't happen in development and only intermittently in a production environment with strict change controls so it may take some time to get the change pushed through (to the latest version). Once done I will capture and send the logs.

Thanks
martin

Re: File Transfer Issue 5.9.5

Please attach complete session (Session.SessionLogPath) and debug log files (Session.DebugLogPath) from the latest version of WinSCP.
KevinV

Sorry, I left out the last bit. The transfer is wrapped in a try/catch and the exception that gets thrown is this:
Timeout waiting for WinSCP to respond

Not sure if that helps.
KevinV

File Transfer Issue 5.9.5

Hello,

We are using the NuGet package 5.9.5 currently and experiencing an oddity when transferring some files. Seemingly randomly the process does not fully complete. Sometime it take multiple attempts but eventually they do work.The below logs are one failed attempt and one successful attempt for the same file transfer, attempted ~20 minutes apart.

When the process fails, the logs look like this:
< 2024-02-21 08:54:51.249 125 Data connection already open; transfer starting.
. 2024-02-21 08:54:51.343 Using TLSv1.2, cipher TLSv1/SSLv3: ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA, ECDHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH     Au=RSA  Enc=AESGCM(256) Mac=AEAD
. 2024-02-21 08:54:51.359 TLS connection established
< 2024-02-21 08:54:51.453 226 Closing data connection, Binary transfer complete.
. 2024-02-21 08:54:51.453 Upload successful
. 2024-02-21 08:54:51.468 Transfer done: 'insert actual file path here' [240]

When the process is successful the logs look like this:
< 2024-02-21 08:35:25.778 125 Data connection already open; transfer starting.
. 2024-02-21 08:35:25.856 Using TLSv1.2, cipher TLSv1/SSLv3: ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA, ECDHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH     Au=RSA  Enc=AESGCM(256) Mac=AEAD
. 2024-02-21 08:35:25.872 TLS connection established
< 2024-02-21 08:35:25.965 226 Closing data connection, Binary transfer complete.
. 2024-02-21 08:35:25.981 Upload successful
. 2024-02-21 08:35:25.981 Transfer done: 'insert actual file path here' [240]
> 2024-02-21 08:35:26.185 Script: exit
. 2024-02-21 08:35:26.186 Script: Exit code: 0
. 2024-02-21 08:35:26.186 Disconnected from server

Is there anything else we could do to troubleshoot where this thing is going sideways? The recipient of the files is becoming impatient with delays we can't seem to control.

Thanks!