Differences
This shows you the differences between the selected revisions of the page.
| 2010-08-24 | 2010-09-16 | ||
| no summary (82.245.151.106) (hidden) | timeout_external_console (martin) | ||
| Line 217: | Line 217: | ||
| ===== [[empty_listing_for_directory]] Server returned empty listing for directory ===== | ===== [[empty_listing_for_directory]] Server returned empty listing for directory ===== | ||
| Check that you have read and execute permissions to the directory. | Check that you have read and execute permissions to the directory. | ||
| + | |||
| + | ===== [[timeout_external_console]] Timeout waiting for external console to complete the command ===== | ||
| + | This error indicates that ''[[executables|winscp.exe]]'' did not receieve an answer from ''[[executables|winscp.com]]'' in time. | ||
| + | |||
| + | Most commonly this happens when ''winscp.com'' has redirected output to a stream with limited buffer. If the stream is not being read from, the buffer gets eventually filled and ''winscp.com'' hangs, when trying to write into it. | ||
| + | |||
| + | In turn the above most commonly happens when ''winscp.com'' is run from another program (such as .Net code), which redirect its output into stream. If the program then e.g. waits for ''winscp.com'' to finish without reading from the stream, the ''winscp.com'' eventually hangs, never finishing. | ||
| + | |||
| + | See example of [[guide_dotnet|.Net]] or [[guide_automation_advanced#inout|WSH]] code dealing with the problem. | ||
| ===== [[error_listing_directory]] Error listing directory ===== | ===== [[error_listing_directory]] Error listing directory ===== | ||