See article dealing with the error in general.

Jmiller76 wrote:

"Timeout waiting for external console to complete the command".

Can you provide me your email address, so I can send you a debug version of WinSCP to track the problem? If you do not want to post the address here, you can send me an email. You will find it (if you log in) in my forum profile. Thanks.

"Timeout waiting for external console to complete the command".

Thanks,
Josh

Jmiller76 wrote:

I am calling WinSCP.com from a VB.NET 1.1 app.
I redirect the output to capture and CreateNoWindow for aesthetics.
With some servers I get the fun "timeout" error.

What timeout do you get? "Timeout waiting for external console"? Or different one?

I am calling WinSCP.com from a VB.NET 1.1 app.
I redirect the output to capture and CreateNoWindow for aesthetics.
With some servers I get the fun "timeout" error.

If I remove the redirected output and disable the CreateNoWindow then all runs fine.

At some point we had a problem downloading files and somewhere in the forum or via trial and error I found that putting a dir command before the download would make things work.

I moved my STDOUT redirect to grab while waiting for the "COM" to finish running rather then reviewing the output after execution.
This showed the problem occurring mid DIR command. If I change the dir command to only look for the file that I need, it continues to the download and succeeds.

I can reproduce the timeout warning, but don't have any documentation on which of our server connections required the initial dir to be inserted.

Thanks,
Josh

This issue has been added to tracker.

Anonymous wrote:

If I use WinSCP in console mode and attempt to connect to a host where I have not copied a key into the authorized_keys file.

Thanks. I'll try that.

If I use WinSCP in console mode and attempt to connect to a host where I have not copied a key into the authorized_keys file.

winscp> open
Host: hostx
Searching for host...
Connecting to host...
Authenticating...
Invalid access to memory
Authentication failed.
winscp>

Beta 4 also issues a memory error when attempting to open a console session where the target host does not a public key installed.

What do you mean by "where the target host does not a public key installed"?

I tried the new beta version with the same results.

Beta 4 also issues a memory error when attempting to open a console session where the target host does not a public key installed.

Thanks for the address (I have removed it). I'll contact you.

So much for using winscp.

Can I have a contact to you, so I can send you a debug version?

WinScp 3.8.2 Build 330
OS- Windows 2003 server

executing the the following always results in a GUI pop up window with the text "Timeout waiting for external console". When I check the remote system only a portion of the files have been transferred before the error occurs. The error usually occurs 45-60 seconds after winscp starts.

Any suggestions to fix ?

etime = DateAdd("s",600,Now)
Set oExec2 = wshell.exec(cmd)
Do until oExec2.Status
wscript.echo Now & " Waiting For Transfer Task to Complete"
wscript.sleep 10000
IF Now > etime THEN
wscript.echo Now & " Transfer did not complete within 10 minutes"
wscript.quit 8
END IF
loop

where cmd = "c:\program files\winscp3\winscp3.com" user@aix3 /ini=d:\cmdlib\winscp\winscp3.ini /script=d:\srm\austin1\ftp_aix3.txt

the script file contains:
option batch on
option confirm off
option transfer binary
rm /var/adm/perfmgr/daily/austin1/*stat*
rm /var/adm/perfmgr/daily/austin1/process*
lcd d:\SRM\AUSTIN1\reports
cd /home/srmserv/junk
cd /var/adm/perfmgr/daily/austin1
put *stat*
put process*
chmod 640 *stat*
chmod 640 process*
exit