We've been seeing a lot of the following in our error logs:
There were some suggestions in the forums that updating to the latest version of WinSCP would eliminate some related problems and we have updated to 5.21.7 - unfortunately we're still seeing a lot of these errors pop up.WinSCP.SessionLocalException: WinSCP process terminated with exit code -1073741502 (C0000142). There was no output. Response log file C:\local\Temp\wscp68E8.00313B98.tmp was not created. This could indicate lack of write permissions to the log folder or problems starting WinSCP itself.
The context of the usage of WinSCP is that we are using it quite heavily in scheduled background processes that read and write files to a SFTP server. The frequency of these processes vary - from once daily to once every 2 minutes. It is entirely possible that the WinSCP process is being invoked by two separate requests at the same / similar time - would this be the cause of the problem?
This exception is being thrown from