login about faq

We are trying to do SFTP (Tectia 6) get for a text file from a remote server. The SFTP works fine when ran from command line. But it fails when ran from SQL Agent 2008. Getting the following error., Any help is much appreciated.

Broker error while opening subsystem: Operation failed (1) error: Could not open connection to `sftpuser@xyz.net': Operation failed14/02/2012 16:30:40:690 SecShUserProcess/secsh_user_process_win.c:421: ssh_userprocess_uninit 14/02/2012 16:30:40:690 SecShUserProcess/secsh_user_process_win.c:285: termhandler thread exiting 14/02/2012 16:30:40:691 SecShUserProcess/secsh_user_process_win.c:332: Terminating 0 processes forcefully. 14/02/2012 16:30:40:691 SecShUserProcess/secsh_user_process_win.c:442: ssh_userprocess_uninit() done. Process Exit Code 4

This question is marked "community wiki".

asked Feb 14 '12 at 22:41

itpowrudu's gravatar image


Apprecaite if anyone can help.

(Feb 15 '12 at 01:19) itpowrudu itpowrudu's gravatar image

Seems to have something with UAC on windows 2008. I have the same issue on a server and when run from an administrator command prompt the connection fails with that error, but when run from a regular command prompt it works fine. Still have not resolved.


answered Oct 31 '12 at 20:38

markrushing's gravatar image


After an hour with ProcMon and Process Explorer, I think I figured it out. Try killing all ssh-broker-gui processes. If that resolves the problem you just need to remove it from C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup.

This seems to have something to do with sftp2 running at a higher integrity level than ssh-broker-gui. When sftp2.exe launches in high integrity (Administrator mode) it calls the broker to handle the key authentication which then tries to make a call back to sftp2. Because the broker is running at a lower integrity it is not able to make the call back to sftp2 which is causing the failure. That’s why the command works when we test it outside of the administrator command prompt. SFTP2.exe runs at medium integrity and so there is no conflict when the broker tries to communicate back.

If you stop the broker processes, when SFTP2 calls the broker to handle the key exchange it launches it with the same integrity level that SFTP2 runs with, so both are running as high and again no issues with the communication back from the broker.

This should only affect Windows 2008 servers.


answered Oct 31 '12 at 21:40

markrushing's gravatar image


edited Oct 31 '12 at 21:40

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: Feb 14 '12 at 22:41

Seen: 7,969 times

Last updated: Oct 31 '12 at 21:40

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