Connect failed SFTP subsystem on server unavailabl - WeOnlyDo Discussion board

Connect failed SFTP subsystem on server unavailabl (General questions)

by kennyblair, Thursday, April 15, 2010, 16:49 (5335 days ago)

Our Network Services group applied an update to one of our servers this past weekend. Since the update my VB6 program, using the WOD SFTP client returns an Connect failed SFTP subsystem on server unavailable error message.

We are using an old version of this client (version 2.2.2). I downloaded an evaluation copy of the latest version of SFTP and was able to connect and retrieve files from the updated server.

I need help to determine if there are any options in the older version that can be changed to make it work.

Re: Connect failed SFTP subsystem on server unavai

by wodDamir, Thursday, April 15, 2010, 16:58 (5335 days ago) @ kennyblair

Hi Kenny,

Unfortunately, the version you're using is *REALLY* old, dating even from 2005. There is no settings that could correct this, since it's basically in the initial connect phase.

The error that you are receiving basically means that SFTP couldn't be initialized for some reason.

If I'm correct the fix that *makes* it work is applied in version 3.2.4 (you can check Release notes here: http://www.weonlydo.com/SFTP/sftp.com.activex.component.asp?rnotes=1).

Unfortunately, we can't make changes to component retroactively, and since you alone mention that latest version works correctly, the only way to fix it is to update your version of the component.

Regards,
Damba

Re: Connect failed SFTP subsystem on server unavai

by kennyblair, Wednesday, April 28, 2010, 17:53 (5322 days ago) @ wodDamir

Hi Kenny,

Unfortunately, the version you're using is *REALLY* old, dating even from 2005. There is no settings that could correct this, since it's basically in the initial connect phase.

The error that you are receiving basically means that SFTP couldn't be initialized for some reason.

If I'm correct the fix that *makes* it work is applied in version 3.2.4 (you can check Release notes here: http://www.weonlydo.com/SFTP/sftp.com.activex.component.asp?rnotes=1).

Unfortunately, we can't make changes to component retroactively, and since you alone mention that latest version works correctly, the only way to fix it is to update your version of the component.

Regards,
Damba


Our network services are corrected the SFTP setup on our server (they moved it to an incorrect folder.

I uninstalled the evaluation version from my second computer, but when I run programs created on my development computer, with the older version, I get a Run-time error '429': ActiveX component can't create object.

What do I need to remove from my 2nd computer to allow me to run programs that I create on my development box?

Re: Connect failed SFTP subsystem on server unavai

by wodDamir, Wednesday, April 28, 2010, 17:59 (5322 days ago) @ kennyblair

Kenny,

Did you distribute your wodSFTP.dll (or wodSFTP.ocx) to your second machine, and register them using RegSvr32?

Regards,
Damba

Re: Connect failed SFTP subsystem on server unavai

by kennyblair, Wednesday, April 28, 2010, 18:11 (5322 days ago) @ wodDamir

Kenny,

Did you distribute your wodSFTP.dll (or wodSFTP.ocx) to your second machine, and register them using RegSvr32?

Regards,
Damba


It has been a long time, but now that you ask, I probably did. I will try re-registering these files.

Re: Connect failed SFTP subsystem on server unavai

by wodDamir, Wednesday, April 28, 2010, 18:18 (5322 days ago) @ kennyblair

Kenny,

The error that you mentioned basically means that there is no component registered on the system, so it can't be initialized.

Regards,
Damba

Re: Connect failed SFTP subsystem on server unavai

by kennyblair, Wednesday, April 28, 2010, 18:19 (5322 days ago) @ wodDamir

Kenny,

Did you distribute your wodSFTP.dll (or wodSFTP.ocx) to your second machine, and register them using RegSvr32?

Regards,
Damba


It has been a long time, but now that you ask, I probably did. I will try re-registering these files.


Thank you, that is exactly what was causing my problem. Sorry to bother you[:smile:]