I suspected below issue was similar to what i had experiencing. It happened approx. 20-30 days. Though, my method is different since I didn't use the .NET library but using scripting command by triggering winscp.com via System.Diagnostics.Process; When Winscp.exe faulted, I need to log off the current user login and re-login again or starting new RDP session.
Appreciate if you could also sent another debug version of WinSCP for me to investigate further about the issue.
Hi. I have a similar issue.
I am using 5.1.3 in our production environment.
Approximately every month WinSCP.exe faults and refuses to work via the .NET library or by running the exe.
When I bring up a new login for the production server (new RDP session) the exe works correctly.
So I have to start our software on a new RDP session which causes unwanted downtime.
Following is the dump from event viewer.
Would really appreciate a fix for this one..
Faulting application name: WinSCP.exe, version: 220.127.116.1181, time stamp: 0x00000000
Faulting module name: WinSCP.exe, version: 18.104.22.16881, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x004ae79a
Faulting process id: 0x1cd0
Faulting application start time: 0x01ce6630f7bee7f0
Faulting application path: D:\Apps\WCFSelfHosted\WinSCP.exe
Faulting module path: D:\Apps\WCFSelfHosted\WinSCP.exe
Report Id: 35a0801d-d224-11e2-a835-005056a3762d