Invalid argument to date encode

Advertisement

Rob2025
Joined:
Posts:
1

Invalid argument to date encode

Hello,

We are currently experiencing a problem amongst our support team when we connect to our remote servers, specifically in directories where files were last modified 2024-02-29 (leap year). We are presented with the below errors.

Directory 1
Unexpected directory listing line '20231121.zip/----------////owner group/889873/0/0/2025/2/29/0/0/1/0/0/1'.
Invalid argument to date encode [2025-2-29]
Directory 2
Unexpected directory listing line '20240229-07230776.zip/----------////owner group/131121/0/0/2025/2/29/23/59/1/0/0/1'.
Invalid argument to date encode [2025-2-29]
I have captured the below from log files
. 2025-03-06 18:32:58.070 Data connection closed
< 2025-03-06 18:32:58.198 226 Transfer completed.
. 2025-03-06 18:32:58.198 Directory listing successful
* 2025-03-06 18:32:58.262 (ECommand) Error listing directory 'C:/Journal'.
* 2025-03-06 18:32:58.262 Unexpected directory listing line '20231121.zip/----------////owner group/889873/0/0/2025/2/29/0/0/1/0/0/1'.
* 2025-03-06 18:32:58.262 Invalid argument to date encode [2025-2-29]
. 2025-03-06 18:33:00.458 Startup conversation with host finished.
 
. 2025-03-06 18:33:03.572 Data connection closed
. 2025-03-06 18:33:03.572 Directory listing successful
* 2025-03-06 18:33:03.835 (ECommand) Error listing directory 'C:/PERIOD/PRINT/PER'.
* 2025-03-06 18:33:03.835 Unexpected directory listing line '20240229-07230776.zip/----------////owner group/131121/0/0/2025/2/29/23/59/1/0/0/1'.
* 2025-03-06 18:33:03.835 Invalid argument to date encode [2025-2-29]
> 2025-03-06 18:33:09.255 REST 0
After the error is received, the directory is not displayed beyond the files which have this date. I have looked into other users experiencing the issue, and attempted a few fixes which have been reported such as Windows DST, but so far I am unable to get around this.

Can anybody offer me some advice on this issue?
Thanks & Regards
  • Error UI.png (9 KB, Private file)

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
41,774
Location:
Prague, Czechia

Re: Invalid argument to date encode

The 2025/2/29 is indeed an invalid date (it says 2025, not 2024). How were you even able to create a file with such timestamp? Do you have many of those? Cannot you just change the timestamps of the files manually on the server?

Reply with quote

Advertisement

You can post new topics in this forum