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.

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

martin

Re: transferoption timestamp remote server ignoring time portion

It's possible with some FTP servers.
See "Timestamp precision" section on
https://winscp.net/eng/docs/timestamp#conversion
To confirm, check in WinSCP GUI shows "times" of the affected files in file panel.

If that does not match your scenario, please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, use /log=path_to_log_file command-line argument. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.
philmcintosh

transferoption timestamp remote server ignoring time portion

I am setting
transferOptions.FileMask = ("*>=" + LastCheckDate.ToString("yyyy-MM-dd:hh:mm:ss"))
but the remote server seems to be ignoring the time portion and sending everything >= just the date portion. Example 2018-04-06:17:09:15 is returning a file with a timestamp of 2018-04-06:05:30:00.
Do I need to format it differently, or is this a problem at the remote end?