In the Task Manager find the Process ID of an instance that failed to close. The process ID is logged in WinSCP session log file, so we can use the ID to look up a log of that instance.

Is there a way to tie them together. This script runs every 60 seconds. How can i tell which ones are left open? Does the log not indicate it was left open?

Zekless wrote:

Yes, Please see the attached log.

The are over 400 sessions in the log. Which of them failed to close?

Any update on this issue?

Yes, Please see the attached log.

Do you have log files of the instances that fail to close?

If I look in my task manager after the script has been running for about a week or so, I see multiple instances of "Console Interface for WinSCP (32 bit)" and "WinSCP: SFTP, FTP, WebDAV, S3 and SCP client (32 bit)" running in my task manager. If unaddressed this consumes alot of the servers resources and eventually starts to cause it to slow down drastically and crash other services. I have attached an image of my task manager.

My script does have an exit command and it does NOT appear to leave an instance running after each time the script fires. It runs every 60 seconds and leaves about 4 of them running a day.

I have updated WinSCP to the latest version at the time of this post which is 5.17.3. The only way I have been able to clean this up is to add a "taskkill /F /IM WinSCP.exe" to then end of the bat file that executes the script. Anyone know what may be going on? Thanks for your help.

Below is an example of the WinSCP script.