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

martin

Re: WinSCP no longer seems to work with scripts which have previously worked corrently

First of all, you have publicly shared your credentials. You must now consider your server and any confidential data stored there compromised. I've deleted the credentials from the script already. But that does not change anything.

Second, the script works for me. If it does not work for you, please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, use /log=C:\path\to\winscp.log 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 can mark the attachment as private.
david.kinraid@...

WinSCP no longer seems to work with scripts which have previously worked corrently

I have recently changed the password on my server. However, WinSCP scripts which worked perfectly well no longer seem to work; in fact the error seems to suggest that the WinSCP command FTPES is incorrect (Unknown command error). The new password is correct - I can log on to the server using it with no issues.

I have attached the script file below with only the password (which is correct in the actual script) omitted.

Any help very much appreciated.