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

Author Message
psharma
[View user's profile]

Joined: 2014-04-03
Posts: 11
Location: India
I am using WINSCP version 5.1.3.

I am using .net library.

My upload/download automation application has been running smoothly for months.

But all of sudden it has started crashing.

It may crash 4 times in 4 hours and sometimes it crash only once in 12 hours.

This happens for small files as well.

Following is the error message which I get;
Timeout waiting for external console to complete the command

Now I have increased the connection timeout to as much as 6 mins (360 sec), but not helping.

I tried setting/enabling "Keepalive" as well, but did not help.

Finally I have now selected the option "Optimize connection buffer size"; not sure if that is going to help.

The connection timeout is still set as 6 mins, though I have removed the keepalive option.

I am not using "Process" rather I am using session.

Please help.
Advertisements
martin
[View user's profile]
Site Admin
Joined: 2002-12-10
Posts: 25034
Location: Prague, Czechia
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.

_________________
Martin Prikryl
psharma
[View user's profile]

Joined: 2014-04-03
Posts: 11
Location: India
prikryl 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.


I just emailed you the log file - Pravin
psharma
[View user's profile]

Joined: 2014-04-03
Posts: 11
Location: India
psharma wrote:
prikryl 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.


I just emailed you the log file - Pravin

OOps, What I shared is WER log report and not WINSCP; I will share the correct one. - Pravin
psharma
[View user's profile]

Joined: 2014-04-03
Posts: 11
Location: India
psharma wrote:
psharma wrote:
prikryl 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.


I just emailed you the log file - Pravin

OOps, What I shared is WER log report and not WINSCP; I will share the correct one. - Pravin


I have emailed you the WinSCP log. Request you to please analyze and share your feedback. - Pravin.
psharma
[View user's profile]

Joined: 2014-04-03
Posts: 11
Location: India
psharma wrote:
psharma wrote:
psharma wrote:
prikryl 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.


I just emailed you the log file - Pravin

OOps, What I shared is WER log report and not WINSCP; I will share the correct one. - Pravin


I have emailed you the WinSCP log. Request you to please analyze and share your feedback. - Pravin.


I just referred to the following post on WinSCP.

https://winscp.net/eng/docs/message_timeout_external_console


Assuming the cause is “limited buffer” of the issue which we are facing, how do we correct it using .Net assembly.

We don’t see any such property under session object of WinSCP.

Kindly assist.
psharma
[View user's profile]

Joined: 2014-04-03
Posts: 11
Location: India
psharma wrote:
psharma wrote:
psharma wrote:
psharma wrote:
prikryl 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.


I just emailed you the log file - Pravin

OOps, What I shared is WER log report and not WINSCP; I will share the correct one. - Pravin


I have emailed you the WinSCP log. Request you to please analyze and share your feedback. - Pravin.


I just referred to the following post on WinSCP.

https://winscp.net/eng/docs/message_timeout_external_console


Assuming the cause is “limited buffer” of the issue which we are facing, how do we correct it using .Net assembly.

We don’t see any such property under session object of WinSCP.

Kindly assist.



Very Happy Very Happy Very Happy Very Happy Issue Finally Resolved Very Happy Very Happy Very Happy Very Happy

In a loop we were using Application.Doevents.
Just removed "Application.Doevents" and the issue just disappeared. Very Happy Very Happy Very Happy Very Happy
psharma
[View user's profile]

Joined: 2014-04-03
Posts: 11
Location: India
psharma wrote:
psharma wrote:
psharma wrote:
psharma wrote:
prikryl 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.


I just emailed you the log file - Pravin

OOps, What I shared is WER log report and not WINSCP; I will share the correct one. - Pravin


I have emailed you the WinSCP log. Request you to please analyze and share your feedback. - Pravin.


I just referred to the following post on WinSCP.

https://winscp.net/eng/docs/message_timeout_external_console


Assuming the cause is “limited buffer” of the issue which we are facing, how do we correct it using .Net assembly.

We don’t see any such property under session object of WinSCP.

Kindly assist.



Very Happy Very Happy Very Happy Very Happy Issue Finally Resolved Very Happy Very Happy Very Happy Very Happy

In a loop we were using Application.Doevents.
Just removed "Application.Doevents" and the issue just disappeared. Very Happy Very Happy Very Happy Very Happy

Refer to caution section under the following post from Microsoft;
https://msdn.microsoft.com/en-us/library/system.windows.forms.application.doevents.aspx
Advertisements

You can post new topics in this forum






Search Site

What is WinSCP?

It is award-winning SFTP client, SCP client, FTPS client and FTP client integrated into one software program for file transfer to FTP server or secure SFTP server. [More]

And it's free!

Donate

About donations

$9   $19   $49   $99

About donations

Recommend

WinSCP Privacy Policy

WinSCP License