Thanks for sharing your solution.

Though note that there's no on error resume next – that's Visual Basic command.
It would abort WinSCP normally, as it's not a recognized command. But it's ignored, because of preceding option batch continue.

If anybody is still searching for simple solution here is a code.
The code is resuming on errors and batch continue ... means if there is a file currently in use - will be simply ignored. But then later I used the keepuptodate command to track the same folder and then sync after file currently in use will be closed.

It simply works perfect.

Well, I have recommended, excluding the file from the synchronization.

You can also try using option batch continue. Though it has a quite broad effect.
https://winscp.net/eng/docs/scriptcommand_option#batch

Another option is to convert your script to PowerShell code with use of WinSCP .NET assembly.
It has more flexibility in handling errors with its Session.QueryReceived event:
https://winscp.net/eng/docs/library_session_queryreceived
You can choose to ignore any errors you like using QueryReceivedEventArgs.Continue.
https://winscp.net/eng/docs/library_queryreceivedeventargs

For some example, see:
https://winscp.net/eng/docs/library_example_recursive_download_custom_error_handling

So what you recommend till there will be any existing solution?

1. Keepuptodate? - backup after outlook has been closed?
https://winscp.net/eng/docs/scriptcommand_keepuptodate

or
2. force close current App and do backup?

or

3. any shadow copy? - means create Temp folder and copy currently used file there and then backup?

Is there an option to ignore the error (maybe with on error resume next) and then any error handler - if there is a Error code 33 then add the Path and file that cannot be synch into some list and then use this list in keepuptodate?

How you solved it? How, anybody of you reading this post, are handling this problem?
If there is any existing bypass solution I will be thankful.

Thank you
Milos

There's currently no simple solution.

All you can do currently, is to exclude the files that tend to be locked from the synchronization.

There are two requests that may solve this:
https://winscp.net/tracker/969
https://winscp.net/tracker/1676
You can vote for them in the tracker.

Hello Martin,

I have another issue I was fighting with and I am not sure what is the best solution, if there exists any switch or what command to use? I synchronize MS Outlook folder on daily basis and Outlook is obviously opened whole day. The error is that when the scheduled script run Outlook is opened at the moment and winscp cannot copy file to server. Of course the same issue with all files that are opened by some windows process/service.

What do you suggest?

here is the error line:
System Error. Code:33 The process cannot access the file because another process has locked a portion of the file

Here is my script:


I am attaching log also.