Re: WINSCP.INI read-only did not fixed the problem
I have sent you an email with a debug version of WinSCP to the address you have used to register on this forum.
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Error writing to file '\winscp.ini' System Error. Code: 32. The process cannot access the file because it is being used by another process
Winscp.ini
to get lock? Because it won't be a Winscp.ini
file to begin with or there is a better approach?
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?
Version 5.15.1 (Build 9407)
I have been using WinSCP .NET Assembly for the last 4 years no problem. A few days ago after I opened the graphical mode and created a new site now randomly I get the message "winscp.ini' System Error. Code: 32. The process cannot access the file because it is being used by another process" I set thewinscp.ini
read-only but still getting the message. Any Idea on how I debug this?
winscp.ini
read-only but still getting the message. Any Idea on how I debug this?
Thanks. That is good to read. Is bug 996 fixed in 5.5 too? I ask because the 5.2.x versions are not released yet.
But, after migrating my server from W2003 to W2008, I get another problem. Somehow, I feel this is related.
In the past 10 days I have run 3x into the problem that (after running fine for days) instantly all started WINSCP sessions fail with ERRORLEVEL 3, without generation any logfile.
The process cannot access the file because it is being used by another process
winscp.ini
to make it read-only and indeed this solved the error. Thanks for your help. :)
winscp /script=<.....>.txt /log=<.....>.log
winscp.ini
to read-write again in order to find out if this is related to my problem. I will post my results here.
Are there any side-effects after making thewinscp.ini
read-only?
What write attempts are done towinscp.ini
?
winscp.ini
read-only? What write attempts are done to winscp.ini
?
Can't create file 'C:\Program Files\WinSCP\WinSCP.ini'.
System Error. Code: 32.
The process cannot access the file because it is being used by another process