login about faq


File transfers above 32Kb are failing when connecting from Tectia Client (sftpg3.exe) to Tectia Server. File transfers were previously working fine. No changes to the client or server configuration were made to cause this. No other client types have this issue (openssh, Tectia GUI).

Here is a typical interaction:


sftp> put largedoc.txt
Error: Cannot open stream listener, file: /appdata/largedoc.txt


2050 Sft_server_stream_write_failed, "2050 Sft_server_stream_write_failed, File name: /opt/data/appdata/largedoc.txt, File handle: 123123123123123, "Error: Cannot open stream listener", Session-Id: 123456"

Workaround ... From the terminal client, I can specify the following which resolves the issue.

sftp> put --streaming=no largedoc.txt

Since no configuration changes were made to the client or server, I assume this issue is the result of something in the network which is not allowing streaming (maybe). Maybe a change to the windows terminal? Ideas?

As a server administrator I am unable to modify how clients connect to my server. For the time being, is there a way to configure Tectia Server to NOT use streaming? Is there some other way of resolving this issue?

asked Oct 06 '14 at 17:12

graham_ashford's gravatar image


Is the same error happening in all server accounts? Or only some? Or even on only one server account?

(Oct 06 '14 at 21:41) Martin Dobsik Martin%20Dobsik's gravatar image

BTW: what version of client and server do you use? On what platform SSH Server is running?

(Oct 06 '14 at 22:22) Martin Dobsik Martin%20Dobsik's gravatar image

There seems to be a bug at least in 6.2.x. The client should obviously transfer the file even is stream listener creation fails; but it does not. It seems that it has been fixed in 6.3.1 on client side.

What versions do you use?


answered Oct 06 '14 at 22:31

Martin%20Dobsik's gravatar image

Martin Dobsik

Hi Thanks for replying ...

We are using Windows Tectia Client Version All other clients are experiencing this issue. As streaming isn't possible from openssh clients, we are not seeing issues there.

The Tectia Server is Linux version

Is the only solution then to upgrade the Client to 6.3.x ?

(Oct 07 '14 at 16:40) graham_ashford graham_ashford's gravatar image

I guess the best would be to find the reason for failure to create the listener. It is known to fail in chrooted account with read only home directory for example. You could try to get the reason from the sft-server-g3 debug log.

(Oct 07 '14 at 21:40) Martin Dobsik Martin%20Dobsik's gravatar image

ok - Solution found. Thank you. I recently changed permissions on the chrooted account such that users could not create directories (or remove directories).

(Oct 07 '14 at 22:04) graham_ashford graham_ashford's gravatar image

You could (perhaps) also solve it by creating writable /tmp directory. Tectia SSH server normally stores IPC Unix domain sockets in /tmp/ssh-<username>/ directory. If that is not possible, it will try to use home directory. And if that is not possible, it fails.

PS: please remember to mark the answer as correct answer if you think it deserves it :)

(Oct 07 '14 at 22:22) Martin Dobsik Martin%20Dobsik's gravatar image
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: Oct 06 '14 at 17:12

Seen: 4,249 times

Last updated: Oct 07 '14 at 22:22

Related questions

All user contributed content licensed under the cc-by-sa license.
Powered by OSQA.