Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
2 years ago
Solved

Data Copy to SFTP Destination Failing

Hello everyone,

I'm currently working on a project that requires sending a CSV file to an external SFTP server. I'm exploring different methods to accomplish this task, and I've decided to try using the Data Copy activity within a pipeline to see if it's feasible.

I've attempted two approaches. Initially, I created a temporary SFTP test server using Free SFTP server: online SFTP server for testing - SFTPCloud and established a connection to it. However, when I tested the connection, I encountered the error "An internal error has occurred." I conducted this test using my personal account, which only has a trial license, as I didn't want to expose my company to an unknown server.



Subsequently, I replicated the same process using my official account, which is associated with an F-64 subscription, and the official external SFTP credentials to which I'll need to send the file. Yet, I encountered the same error.

Could someone provide insights into what might be causing this issue? Any ideas on how to troubleshoot and establish a successful connection would be greatly appreciated.

Thank you!

  • Anonymous's avatar
    Anonymous
    2 years ago

    Hi Anonymous ,

    Thanks for using Fabric Community.
    I tried to repro your scenario -

     


    Can you please check this format?

    eu-central-1.sftpcloud.io:22

     


    Hope this is helpful. Please let me know incase of further queries.

4 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi Anonymous ,

    Thanks for using Fabric Community.
    I tried to repro your scenario -

     


    Can you please check this format?

    eu-central-1.sftpcloud.io:22

     


    Hope this is helpful. Please let me know incase of further queries.

    • Anonymous's avatar
      Anonymous
      Not applicable

      Thank you! I didn't expect the solution to be so simple.

    • ToddChitt's avatar
      ToddChitt
      Super User

      What is the proper format for specifying a non-default port?

      <serve rname>:<port number>

      or

      <serve rname>(:<port number>)

       

      The latter seems to be what Fabric recommends when creating the connection:

       

      But the former is how you suggest here.

      I can't get ANY flavor to work in Fabric.

       

      Any additional nuggets of wisdom?

      Thanks

  • Anonymous's avatar
    Anonymous
    Not applicable

    Thank you! I didn't expect the solution to be so simple.