@jwatkin

(Different guest)

The 0 byte, that person stated they felt it was the FTP server. Indeed, it can be. Anything that interrupts the data stream can potentially create a 0 byte file. If the file is created then something happens after that before the data is sent, it could result in a 0 byte file.

Really, if the server sees an error like on opening a file, it could do this. Even opening a port but having a port error will do this as the port is expected to change. There are many things that can go wrong that could potentially do this.

I had the same problem with 0 bytes uploaded but when I disconnected my VPN connection it works just find

Unfortunately I don't believe we were ever informed of the exact issue with the vendor's FTP server or their network. I'm deliberately including the possibility that it was a network issue on the vendor's end based on vague recollections. We're no longer using that vendor so I can't ask them nor see our old tickets in their tracking system.

I checked my email logs. In addition to erroneously uploading some files as 0 bytes, some files were partially uploaded too, the affected files would contain some data but not all of their data. The latter part of a file's data would be randomly truncated.

Do you know what exactly was the issue with SFTP server setup?
We have the exact same scenario wherein some random files are transferred as 0 kb files, but infact they have data.

After further testing, we believe the problem is with our vendor's new FTP server, configured just for us, and not WinSCP.

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

The previous post from "Guest" was from jwatkin, as is this post.

I had a colleague attempt the same FTP transfer with a different computer, from a different network, using a different FTP client. On his first attempt he also had one file incorrectly transfer with 0 bytes. However on subsequent attempts, he had no files incorrectly transfer with 0 bytes. Even so, given that he had one instance of this error, the problem isn't isolated to WinSCP.

When I tried again with my WinSCP client on my computer, I had a couple of files incorrectly transfer with 0 bytes.

My question still stands though. Is there a way for WinSCP to validate each file transfer byte-for-byte and report any discrepancies?

Thank you.

I've been successfully uploading files to our CMS vendor's FTP server for years with WinSCP. They've configured a new FTP server for us, which only we are able to use. Each customer gets their own FTP server. Now some of the files that I upload with WinSCP 5.15.9 (build 10071) to this new FTP server are arriving there with 0 bytes when in fact they have content. In a directory with 66 files, two were transferred with zero bytes when they shouldn't have been. When I repeat the transfer, a different couple of files are incorrectly arriving with 0 bytes. It appears to be random.

I'm not seeing any errors or warnings in the WinSCP client GUI during these transfers. This issue was discovered later when our site threw an exception. I've since enabled WinSCP logging. I don't see anything in the log file that stands out, but I'm unfamiliar with these log files.

What sort of validation does WinSCP perform to make sure files are being transferred accurately?

I will try having a colleague replicate the problem with their machine and a different FTP client. If they have the same problem, then I presume the problem is with the vendor's FTP server that they have set up just for us.

Thank you.