Skip to main content
Solved

Problem with FTPCaller and SFTP

  • October 9, 2020
  • 3 replies
  • 224 views
K
Forum|alt.badge.img

Hello,

I want to use a FTPCaller to push a file on a SFTP server. It doesn't work on my Windows 10 PC, but on another PC it works fine. And on my computer, I can access to the SFTP server using Filezilla or Winscp.

 

I'm using FME workbench 2019.1.1.0 (20190801 - Build 19617 - WIN64) on Windows 10 version 1903.

 

I get the error :

"

FTPCaller (FTPFactory): FTP info:  Trying XXX.XXX.XXX.XXX:22...

FTPCaller (FTPFactory): FTP info: TCP_NODELAY set

FTPCaller (FTPFactory): FTP info: Connected to XXXXXXXXXXXX (XXX.XXX.XXX.XXX) port 22 (#0)

FTPCaller (FTPFactory): FTP info: Failure establishing ssh session: -43,

FTPCaller (FTPFactory): FTP info: Closing connection 0

FTPCaller (FTPFactory): HTTP/FTP transfer error: 'Failed initialization'

"

 

I join the full log of my workspace, with Debug option, if it helps.

Best answer by chrisatsafe

It's possible that this may be related to an issue that was recently fixed as well (FMEENGINE-61616). Could you try in build 19639 or newer to see if the issue is resolved?

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

3 replies

steveatsafe
Safer
Forum|alt.badge.img+13
  • steveatsafeSafer
  • Safer
  • 422 replies
  • October 16, 2020

@kukur​ 

On the system that it works, have you compared the log file?

I am assuming you are using the same workspace, the same version of FME Desktop, and that the computer is in the same network or data centre?

 

FYI: this is a very similar trail of logging:

https://github.com/curl/curl/issues/4041#issue-457711302 (not super helpful but might indicate a permission issue somewhere).

 

SteveatSafe
chrisatsafe
Contributor
Forum|alt.badge.img+2
  • chrisatsafeContributor
  • Contributor
  • 606 replies
  • Best Answer
  • October 16, 2020

It's possible that this may be related to an issue that was recently fixed as well (FMEENGINE-61616). Could you try in build 19639 or newer to see if the issue is resolved?

K
Forum|alt.badge.img
  • kukur
  • Author
  • 4 replies
  • October 19, 2020

It's possible that this may be related to an issue that was recently fixed as well (FMEENGINE-61616). Could you try in build 19639 or newer to see if the issue is resolved?

It seems to be that. I launched my job with FME 2019.2.3.1 (build 19643) and it worked perfectly.

 

Thanks.

Community Stats

32,070
Posts
121,781
Replies
39,699
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.