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: Invalid argument to date encode 5.5.4

Thanks for your report.
I have sent you an email with a debug version of WinSCP to address you have used to register on this forum.
BenRacicot

Invalid argument to date encode 5.5.4

The Log Only says exactly what that error is. Same as the screenshot I had attached. (that's why I omitted it, sorry for not declaring that)
Apparently the error only happens when I try to upload new files from my local install to a server env.

Thanks for getting back to me! :)
martin

Re: Invalid argument to date encode 5.5.4

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

To generate log file, enable logging, log in to your server and do the operation and only the operation that causes the error. 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.
BenRacicot

Invalid argument to date encode 5.5.4

Hello all,

I thought I'd reach out here about the "Invalid argument to date encode" error. I see the most recent ticket for this issue was in September. Is there any type of fix for this?
(I'm trying to move local files from my WAMP install to a live server environment)

I've tried some of this fixes that have worked for others such as resetting the OD's timezone.

WinSCP version 5.5.4
Windows 7 Professional