geek_jumper wrote:

Is this issue fixed in WinSCP's latest version? I was using WinSCP 4.1.8. It was running fine in Windows server 2003(32 bits) version. Now I am running in Windows Server 2003(64bits) OS. In this OS I am frequently receiving this type of error. After rebooting server, it is running smoothly for some days and after that I am receiving the same error. Please let me know, If this bug is fixed in latest version's of WinSCP.

I do not know. But you should upgrade anyway.

Is this issue fixed in WinSCP's latest version? I was using WinSCP 4.1.8. It was running fine in Windows server 2003(32 bits) version. Now I am running in Windows Server 2003(64bits) OS. In this OS I am frequently receiving this type of error. After rebooting server, it is running smoothly for some days and after that I am receiving the same error. Please let me know, If this bug is fixed in latest version's of WinSCP.

The bug entry in the tracker doesn't show anything but have there been any updates to this bug? Thanks

M Usman wrote:

I am getting these two errors once in a week.
....

Are you able to reproduce these with the latest version? 4.1.9 or even better with 4.2.3 beta?

Hi,

I am getting these two errors once in a week.

1) Reporting queued error: faulting application WinSCP.exe, version 4.1.5.410, faulting module kernel32.dll, version 5.2.3790.4062, fault address 0x0000bee7.


2) Faulting application WinSCP.exe, version 4.1.5.410, faulting module kernel32.dll, version 5.2.3790.4062, fault address 0x0000bee7.

Only workaround is to reboot the server but it comes back again after 3-4 days.

Please help

Regards
Usman

That's fine.
Thanks so much for all your efforts!
You're a credit to the open source world, giving support like that.
Don't worry that we couldn't figure it out. I've managed to hack together a solution with Putty PSFTP so don't lose any sleep over it.
Thanks again.

This bug has been added to tracker.

Hi, I got your second debug version, tried it, and this time it did generate a log file. I've emailed it to you. Cheers.

I just got your email with the debug version. I've tried it and sent you the results - however it crashed before it got a chance to create the trace file.
Thanks for your help.

Thanks for the response.

Okay i've emailed you from my work account (different email address than the one i registered here with). You can respond either way.

Can you send me an email, so I can send you back a debug version of WinSCP to track the problem? Please include link back to this topic in your email. Also note in this topic that you have sent the email. Thanks.

Another thing: Tried using version 421, it had the same error.[/i]

One more thing: I'm using the Portable Exe version.
Is that enough details?

Firstly, thanks so much for a good product.

Hi, I get this error when i call winscp from a scheduled task (the error details are from the event log):

"Faulting application winscp419.exe, version 4.1.9.416, faulting module kernel32.dll, version 5.2.3790.4480, fault address 0x0000bef7."

My scheduled task runs as the "NT AUTHORITY\SYSTEM" user. It runs a batch file with this contents:

winscp419.exe /log="logs\%date:~10,4%%date:~7,2%%date:~4,2%_winscp.log" /script=xxx.txt

Note the /log=... above - this log file does not get generated at all, so i don't know whats crashing.

My script 'xxx.txt' looks like this (censored a bit) :

option batch on
option confirm off
option transfer binary
open abc:def@xyz -hostkey="ssh-rsa 1024 12:34:...."
get -delete /remotefolder/* "D:\localfolder\"
close
exit

Interestingly, when running this batch file from my normal account, i have no issues.

Any ideas?