Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

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


Re: Overwrite file question

I certainly can – thank you for the reply!

Re: Overwrite file question

No. But you can delete the files before the upload, cannot you?

Overwrite file question

Hi - I am using a script to PUT a file onto a server which does not allow me to overwrite files but does allow me to PUT new files, delete files, and re-name files. My goal is to replace one or more files that may already exist in the target folder.

After researching the forums for a while it seems one way to implement this is to use RESUMESUPPORT as this will transfer my file to a new file name, delete the existing file, and rename the transferred file from its temporary name to a permanent name.

This mostly works as expected but once I try to transfer the file for the 2nd time I get this message:
> 2022-01-25 15:44:38.138 Type: SSH_FXP_LSTAT, Size: 37, Number: 519
< 2022-01-25 15:44:38.170 Type: SSH_FXP_ATTRS, Size: 37, Number: 519
. 2022-01-25 15:44:38.170 File exists: Test.csv;-;25;2022-01-25T21:43:04.000Z;3;"" [0];"" [0];rwxrwxrwx;1
. 2022-01-25 15:44:38.170 Existing file looks like a symbolic link, not doing resumable transfer.

Using scripting (via cmd.exe) is there any way to avoid this and force WinSCP to perform a transfer with resume support despite the symlink?