Hi Martin, I work with
@dranaware, who opened this case, and wanted to try and help provide more context on the issue we saw. WinSCP is being used by an internal application programmatically. Our exe calls WinSCP and tells it to move files from one location to another on a regular cadence. This was setup in November 2024 and was working just fine until February 17th. On February 17th at 4:34AM MT the logs from WinSCP just stopped. It seems it ran successfully and would/should have been ready to run the next time it was called. However for the next 4 days (until it was noticed) WinSCP never ran when called, never logged any details, and never showed any error message. The support team finally noticed it had not been running and, as a workaround, set it up to run from the server D drive rather than the C drive where it had previously been running. This worked and WinSCP has been running just fine ever since. What we are trying to understand, and find the root cause of, is why WinSCP just stopped responding/running on February 17th until it was noticed and required manual intervention to get it going again. Another thing that was noticed, 12 minutes after the last log entry from WinSCP, on that same server, a file simply called
Program with no extension, was created in the C drive. This caused the server itself to complain as many applications require the
C:\Program Files\... location to be available and having something called
C:\Program could disturb those processes. We have dealt with the rogue file and removed it. We also experimented in our non-production environment trying to reproduce that scenario to see if a file named
Program sitting in
C:\ would cause an issue for WinSCP. In the non-prod environment there was no issue, WinSCP was called and ran as expected and moved our files. So it appears this
Program file is just a red-herring but wanted to mention it as that is the only other strange thing we see occurring at or around the same time that WinSCP stopped responding. Our internal server team has analyzed the server, we have had Microsoft do a full diagnostic, we had the DB2 DBAs and their vendor do an analysis (the
Program file had details related to DB2 stats inside it), we had our DNS team investigate any possible DNS issues and all have turned up empty in terms of a root cause. You are our last resort. Have you ever heard of or seen anything like this with WinSCP?
