Your best friend for file transfer.

Fetch application logoFetch

Not making a connection after another send (2 posts)

  • Started 2 years ago by JimBrandt
  • Latest reply 2 years ago from Jim Matthews
  • JimBrandt Member

    Jim

    I have a script that is attached to a Watch folder (to carry on a previous discussion).

    This script reads a file to get file location and FTP credentials and uploads that file to the specified FTP site, then sends an email to a list of email address also defined in the dropped file to notify them of the upload. This all works almost flawlessly, but I have a situation that is causing strange behavior.

    I have one group of uploads that all use the same FTP site, but each has their own login. Any time I try to upload to any of these users, the script cannot complete the upload because it errors out trying to obtain the initial list of files. (no I haven't looked at the transcript window).

    If I drop this same file into the watch folder so it is the first transfer being attempted, it connects correctly, showing the list of files at the remote location and promptly uploads the file I'm wanting to send.

    My question: is there something from a previous login that I should be looking for that would cause the next login attempt to not allow a file list to be shown? It seems logical that it is the prior activity that is interfering with the current login attempt, so I need to know to look for.

    Jim Brandt

    Edited 2 years ago #

  • Jim Matthews Administrator

    I would want to look at the transcript. My first thought is that maybe the upload is incorrectly re-using a transfer window that is logged into a different username. That could interfere with an attempt to get a file list for a folder that isn't there. But maybe you've considered that possibility already.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 2 years ago #

Reply

  • Or nickname, if you prefer.
  • This will be kept confidential.
  • This is to ensure that you’re a person, not a spambot.