Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

seyedahmed

Re: Error on 2003 server

martin wrote:

Please attach a full log file showing the problem (using the latest version of WinSCP).

To generate log file, use /log=path_to_log_file command-line argument. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you may email it to me. You will find my address (if you log in) in my forum profile. Please include link back to this topic in your email. Also note in this topic that you have emailed the log.


Please see the attached file for logs

Thanks
Seyed
martin

Re: Error on 2003 server

Please attach a full log file showing the problem (using the latest version of WinSCP).

To generate log file, use /log=path_to_log_file command-line argument. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you may email it to me. You will find my address (if you log in) in my forum profile. Please include link back to this topic in your email. Also note in this topic that you have emailed the log.
seyedahmed

Error on 2003 server

I have a console app (VB.NET) very similar to the example code presented on this site. When run interactively, it can upload/download via SFTP without issues. When run via a Scheduled Task, it runs silently without issues. However, when my RDP session to the server disconnects, the Scheduled Task runs, but WinSCP fails with error messages like this:


The WinSCP executable appears to have crashed. Log file C:\Documents and Settings\MyServiceAccountName\Local Settings\Temp\tmp112F.xml does not exist.

Please see the attached file for logs

Is there something special about running WinSCP from a console app running as a scheduled task that would cause this type of behavior?

Thanks
Seyed