was a typo, I meant winscp
The error I got few times was:
Cannot open file "C:\tbass\rest\winscp.ini". The process cannot access the file because it is being used by another process
The solution was to pre-create winscp.ini file during deployment as was reported here on forum several times as solution for this (it works, I didn't get error after that) and I did it with above PowerShell code. I can not give you logs from when error occurs because debug & session log make huge performance difference (x2) so I disabled it after I sent you the data and I don't want to wait for this error weeks in production with such performance issue. You obviously can see in those logs that
is there and I shouldn't get this error.