Topic "WinSCP stops after error, even with batch mode"

Author Message
irrupt

Guest


< 2016-07-05 02:16:57.606 Script: Invalid argument to date encode [30828-11-1]

This is the error I got

. 2016-07-05 02:17:06.653 Script: Failed
> 2016-07-05 02:17:06.669 Script: close
. 2016-07-05 02:17:06.872 Disconnected from server

Then it just quits, doesn't try to continue

It's from a file that has an improper modified date (it's just a time - 12:00 to be exact, no date for some reason)

Is there any way that someone could make it so WinSCP will just continue on it's merry way afterwards?

WinSCP and OS versions are:

. 2016-07-05 02:00:06.606 WinSCP Version 5.7.7 (Build 6257) (OS 6.1.7601 Service Pack 1 - Windows Small Business Server 2011 Standard)
irrupt

Guest


How hard would it be to just check the files modified time and if it's $null or invalid, ignore it in the sync process?

I have been using WinSCP with Powershell for some time and it was working fine until I came across this problem.. I've solved it myself however using Powershell - just made a function to check the files lastwritetime propery and if it's $null it's added to an array that's used in the #exclude directive.
martin
[View user's profile]
Site Admin
Joined: 2002-12-10
Posts: 25034
Location: Prague, Czechia
Please attach a full session log file showing the problem (using the latest version of WinSCP).
_________________
Martin Prikryl
Advertisements

You can post new topics in this forum






Search Site

What is WinSCP?

It is award-winning SFTP client, SCP client, FTPS client and FTP client integrated into one software program for file transfer to FTP server or secure SFTP server. [More]

And it's free!

Donate

About donations

$9   $19   $49   $99

About donations

Recommend

WinSCP Privacy Policy

WinSCP License