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

KOK HO

System Error. Code: 32.

I keep having the following error everyday when I run the script to keep update from one server to another

The process cannot access the file because it is being used by another process")
Script: Can't open file 'D:\xxxx,dat'.
Script: System Error. Code: 32.

any suggestion to trace the file is being used by what process?

I'm using "Process Explorer" but can't find this xxxx.dat is in used by any process
saarja

how about script

hi, ok there is a gui option for continue error but i'm using script, is there swich for that ?
saarja

still no workaround for this file in use error ?

it could be nice if file in use error 32 could be continue/ignore and move next file.
Guest99

Re: Any updates on this?

Is their any options to allow for skipping when this condition happens...I have this same problem too...look like this has been a problem for almost 5 years now...shocked that it has never been fixed....

chippy wrote:

Is there a hidden preference somewhere to automatically skip files for which this error occurs?
chippy

Any updates on this?

Is there a hidden preference somewhere to automatically skip files for which this error occurs?
edwardb

got this error also

Hi I got this error also when using this parameter:

C:\>winscp /console /command "open run_sync" "synchronize remote -delete" "keepuptodate -delete"

Hope you can resolve it. Thank You
martin

Re: System Error 32 using "Keep remote directory up to date"

Thanks for your post. This request has been added to tracker.
flxkid

System Error 32 using "Keep remote directory up to date"

System Error. Code: 32.
The process cannot access the file because it is being used by another process

I'm using WinSCP to transfer backup images from one machine to another nightly just using the simple "Keep remote directory up to date" feature. I get this error every nite while it attempts to transfer the backup image while it is still being written to. Is there a way to make WinSCP just ignore this error? If it ignores it, everything will still stay up to date since as soon as the file is unlocked by the backup process, WinSCP will grab it. Right now, I have to clear the error on that machine daily after which the file is transfered just fine.

Thanx,

OLIVER