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

fatlump wrote:

Yes, but I am trying to communicate via SFTP...??

Well, I do not have a log for your SFTP attempt, so I can only repeat: That probably means WinSCP failed to negotiate SFTP protocol and fell back to SCP (that's default behavior). It does not seem that WinSCP can communicate with your server in any way.
fatlump

Yes, but I am trying to communicate via SFTP...??
martin

scp: not found

The scp binary is either not present on the server or is not in PATH.
fatlump

I'm sending the log as private.

Basically, I am able to browse the remote folders, but as soon as I try to download anything, it doesn't work.

Thanks.
martin

fatlump wrote:

The error message states to use SFTP instead of SCP, but when I first connected to my remote host, I definitely selected the default option, which is SFTP.

Is it somewhere ELSE that I should select "SFTP" or was it refering to when I connect initially?

That probably means WinSCP failed to negotiate SFTP protocol and fell back to SCP. It does not seem that WinSCP can communicate with your server in any way.

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

To generate log file, enable logging, log in to your server and do the operation and only the operation that causes the error. 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.
fatlump

Hi,

I am having the same issue: When I try to edit a remote file, I get the following error message: "Cannot execute SCP to start transfer. Please make sure that SCP is installed on the server and path to it is included in PATH. You may also try SFTP instead of SCP. Command failed with return code 127."

My environment: Windows 7 and the remote server is a crappy Western Digital Sharespare, apparently running Linux: "Linux version 2.6.12.6-arm1 (arsene@localhost1) (gcc version 3.4.4 (release) (CodeSourcery ARM 2005q3-2)) #47 Mon Aug 16 16:23:50 CST 2010"

The error message states to use SFTP instead of SCP, but when I first connected to my remote host, I definitely selected the default option, which is SFTP.

Is it somewhere ELSE that I should select "SFTP" or was it refering to when I connect initially?

Any other suggestions?

Thanks
martin

Re: Anyone seen this Error?

Please read FAQ. If that does not help, come back.
bobmorgan

sorry i forgot to sign in to forum first - the post is mine (BobMorgan)
Guest

Anyone seen this Error?

seeing the following pop up box error:

Copying files from remote side failed.

Cannot execute SCP to start transfer. Please make sure that SCP is installed on the server and path to it is included in PATH. You may also try SFTP instead of SCP
Command failed with return code 127



WinSCP version is 4.0.6 (build 358)
I checked PATH and verified link to scp (we are testing quest_Openssh along with quest_putty using GSSAPI)