@MikeLindsey: Like:

See https://winscp.net/eng/docs/scriptcommand_put

Where do I put the -resumesupport=off?

I run a batch file that contains this:

Here's the scp file:

Thanks!

Thanks for your feedback.

Hi, just a quick update to say that this issue seems resolved. Apparently, the pollers at the receiving end could (would) not be changed to ignore fileparts. They're pretty confident that they can recognise files in the process of being transferred so won't pick up partial files. So their steer was definitely to disable the resume transfer option causing the fileparts.

It did seem that changing the default settings to do this was not being reflected in the actual transfer as run from an automated script.

So I amended the settings and then exported them to an ini, and then referred to that ini when calling winscp.com with a script file. Since making this change, the issue has not re-occurred.

Thanks for the help.

Anonymous wrote:

Although ... if the 'transfer resume' function is what creates the .filepart files and that function is successfully disabled, then what happens during the transfer? If a file is halfway transferred, then what is actually in the destination folder? Is it half a file of the same name e.g. File1.pdf? If the polling tool took this instead of the .filepart, then this would be worse.

Yes, half file of the same name. I'd suggest you to use the temp folder solution. Or alternatively, keep the current way with .filepart files and modify your polling function to ignore these files.

Sending to a temp folder sounds like the winner in this scenario.

Although ... if the 'transfer resume' function is what creates the .filepart files and that function is successfully disabled, then what happens during the transfer? If a file is halfway transferred, then what is actually in the destination folder? Is it half a file of the same name e.g. File1.pdf? If the polling tool took this instead of the .filepart, then this would be worse.

Or is it that .fileparts are created for all transfers and the transfer resume function simply allows broken transfers to be resumed? In which case, I'll go directly to a temp folder solution.

Use -resumesupport switch.
See https://winscp.net/eng/docs/resume#switch

---

Though not sure if disabling resume support really helps. It probably won't prevent the polling function from picking up a partially transferred file. Consider uploading the file to an intermediate directory. Once uploaded, move it using mv command to the destination directory.

Hi, I'm using v4.3.5 on a server to SFTP some PDFs on a daily basis. The transfer job is automated using a .bat file which calls:

The script looks like (comments removed):

Pretty standard stuff. I'd like to disable the resume transfer option. It's causing us an issue as the server we SFTP the PDFs to has a polling function which takes anything that arrives and passes it on. If a file transfer is in process or there's a connection issue, then there's a .filepart file in there that gets picked up and moved on to the destination. Sometimes the transfer resumes successfully and the destination will have both a .pdf.filepart and a .pdf. Sometimes it does not and the destination will have a .filepart and a .pdf of zero bytes.

I can untick the Resume Transfer option in the Preferences in the client app on the server and Disable the Endurance. But we're still getting fileparts. Is this because we're running the transfer from a script and that uses default options and not options changed in the client app? Any way that I can disable this option?