The error shows again the exact error is:
Error writing to file '\winscp.ini' System Error. Code: 32. The process cannot access the file because it is being used by another process
The lock is very quick because a second after the error the scrip goes again for a different file and it works.
If I set in
Preference\Storage\Configuration storage to use
Windows Registry it will better for preventing
Winscp.ini
to get lock? Because it won't be a
Winscp.ini
file to begin with or there is a better approach?
Thanks!
Albert Torres
AN UPDATE 5/20/2021
I set on the configuration storage to use
Windows Registry. When I do that the
winscp.ini
get deleted fine so far, but when I run the script the
winscp.ini
gets created back and if I open
Winscp.exe
the setting returns to
Automatic INI file. I have the same script and same
winscp.exe
version on another server there I set to use
Windows Register as well and when I run the script the
winscp.ini
it keep the setting just fine and it does created the
winscp.ini
file. Any idea why has different behavior from one server to another?
Thanks
Albert Torres