after uploading the file continues to be in upload not allowing to go to Toggle.

sorry for my english

I'm sure many people have the same need.

To copy a file, then based on a successful copy, delete the source file.

BUT if the copy fails, leave the source alone for a retry.

This is usually known as a Move.

This facility exists in FTP Voyager for manual operations, but I can't work it out in the scheduler.

Anybody got an idea?

I've had FTP Voyager and FTP Scheduler installed for many years.

On 11/2/2012 the scheduler stopped running nightly backups and now only generates errors when manually executing the jobs.

"Could not retrieve additional information about the local path. Please make sure the path exists and the local user has permissions".

This system has been setup for years and has not changed. The FTP Voyager can manually connect to the profile and I can download files from the server manually without problems.

The only major change to the system were recent FTP software upgrades and patches.

I've double checked the FTP Scheduler Profiles (which never changed passwords in the first place).

I've added a brand new FTP folder with new login password to the server which connects in FTP Voyager, but generates the same errors when manually executing a synch job in FTPV Scheduler.

And I've tried restarting the FTP Voyager Scheduler service and rebooting.

Also nothing has changed on the server and all the files and folders have full read/write access (and can be copied down manually from the FTP Voyager).

Its only when executing the job from within FTP Scheduler that it now fails with these messages and it started around 11/2/12.  But I can't recall on what dates I applied the FTP software patches and upgrades.

Good day

I've set up a Scheduler job to Move Down files from an FTP server to my local disk.

The files download fine but then the remote files are never deleted, I don't even see a failed DELE command in the log.

I've tried the following two remote paths:

• /
• /*

Both work for downloads, both don't delete the files.

Log Sample

[03] Sat 12Apr14 17:04:37 - Receiving: /folder/blah.avi -> C:\Users\Private\Downloads\blah.avi

[05] Sat 12Apr14 17:04:37 - PASV

[06] Sat 12Apr14 17:04:38 - 227 Entering passive mode (95,211,93,130,234,161).

[03] Sat 12Apr14 17:04:38 - Opening passive mode data connection to 95.211.93.130, port 60065.

[05] Sat 12Apr14 17:04:38 - RETR /folder/blah.avi

[06] Sat 12Apr14 17:04:38 - 125 Data connection already open. Transfer starting.

[06] Sat 12Apr14 17:22:55 - 226 Transfer complete.

[03] Sat 12Apr14 17:22:56 - Transferred 358 649 864 bytes. 201,12 KB/sec.

[05] Sat 12Apr14 17:22:56 - XCRC /folder2/blah2.avi"

[06] Sat 12Apr14 17:22:56 - 500 Command "XCRC" not understood.

[04] Sat 12Apr14 17:22:56 - XCRC command failed. The command may not be supported by this server.

[03] Sat 12Apr14 17:22:56 - XCRC command checking has been disabled for future transfers using this session.

[03] Sat 12Apr14 17:22:56 - Received 358 649 864 bytes.

[03] Sat 12Apr14 17:22:56 - Transfer time: 00:29:01.453.

Any help to fix this or workaround would be much appreciated.

Hello,

I have setup a FTP Voyager Scheduled Task that will not executing.  The task is setup to reach out to a FTP to move down any available files and also move up any new files that have been created locally.

When the task is scheduled, it will not stop executing and no available files are pulled down from the FTP or moved up to the FTP site.

Any help is appreciated.

Thanks

I've been a long-time user of FTP Voyager, well before SW bought up RhinoSoft.  I even paid for it too, back in those days.  However, lately I upgraded to the new version, and found out that hey!  It's free now!  Cool!

However, all was not sunshine and roses.  I too have run into the FTP Voyager Scheduler empty folder bug, wherein you perform a "Move Down" command against an empty folder and it simply sits there.  In my case, it performs KEEP ALIVE tasks to hold the connection open.  Critically, because this task is still executing, it will not execute any of the other scheduled tasks.  See below for a log output.

[03] Fri 05Dec14 14:15:49 - Getting "real path" name to keep connection alive (KEEP ALIVE)

[07] Fri 05Dec14 14:15:49 - SSH_FXP_REALPATH: translating path: .

[08] Fri 05Dec14 14:15:49 - SSH_FXP_NAME: translated path: /

[03] Fri 05Dec14 14:18:49 - Getting "real path" name to keep connection alive (KEEP ALIVE)

[07] Fri 05Dec14 14:18:49 - SSH_FXP_REALPATH: translating path: .

[08] Fri 05Dec14 14:18:49 - SSH_FXP_NAME: translated path: /

I see that this is a known issue here on the forums, and that there are supposidly "bug fix requests" or something to handle it.  However, I have a problem with this NOW.

I believe I found a simple work around.  I chained a file upload to the destination folder first, uploading a single 1-byte file to the destination, and THEN performing the full folder move down.

This will always cause the remote folder to have something in it, and for then the task to complete successfully.  I then set up my local-side automation to ignore that file, and things were working.

Not exactly elegant, but it's working for now. :-/

I'm using ftp Voyager at a daily basis to check remote sites and move down all files.

The task works almost every day. Exception are when the remote ftp site is empty. Here the task will run continuously.

I've tried to turn off keep alive, but it continues to run forever.

I'd like the task to fail, if no files.

Anyone knows what i'm doing wrong?

Thanks.

Hi,

We are using FTP Voyager version 16.0.2.0 with 2-3 tasks configured but sometimes if one of the task stuck all other will be stuck in queue. i checked the logs of task which was stuck & showing below logs.

[13] Tue 25Nov14 14:23:00 - (Action: "/Source/Data" to "D:\DataLoad\In") - Action failed (Last Error Message: Unable to perform file action: Could not retrieve additional information about the source path.  Does the source path exist?).

[12] Tue 25Nov14 14:23:00 - (Task: Source File Receive from SAP) - Execution failed (Last Error Message: Unable to perform file action: Could not retrieve additional information about the source path.  Does the source path exist?).

[12] Tue 25Nov14 14:23:01 - (Task: Source File Receive from SAP) - Next scheduled execution on Tuesday, November 25, 2014 14:32:57

[05] Tue 25Nov14 14:23:04 - QUIT

[06] Tue 25Nov14 14:23:06 - 221 Goodbye.

[12] Tue 25Nov14 14:32:58 - (Task: Source File Receive from SAP) - Performing scheduled execution of task for Tuesday, November 25, 2014 14:32:57.

[12] Thu 27Nov14 11:04:10 - (Task: Source File Receive from SAP) - Execution was aborted.

I manually ended the task & run it manually & it's completed sucessfully. Kindly suggest what could be the proble & how to resolve it.

Regards,

Dhiraj

So the Move Down functionality in FTP Voyager Scheduler is not consistent with what one would typically call a file move operation.  Previously, in version 15 of FTP Voyager, a Move Down operation behaved like this:

1. Get list of all files at destination.
2. Copy remote file to local destination.
3. Delete remote file.
4. Go to next file on list.
5. Continue until list is empty.

Now, however, version 16 behaves like this:

1. Get list of all files at destination.
2. Copy remote file to local destination.
3. Go to next file.
4. Continue until list generated at step 1 is complete.
5. Delete all remote files at destination, regardless of what was contained in list generated at step 1.

Effectively it is just the Download and Delete Remote Path commands chained together.  This is a big problem for my automation, as I cannot guarantee that the folder won't have new files created in it during download operations #2-4, which will then ultimately get deleted by step #5.

So long story short, can the behavior be reverted to the v15 style of move?

Using Ver. 16.1.0.0, manual Synchronization works fine, but when scheduled using Schedule Management Console Synchronization fails, here are the logs.

Thanks,

B

This when it fails

[03] Fri 01Aug14 14:29:01 - Server supports resume.

[05] Fri 01Aug14 14:29:01 - OPTS UTF8 ON

[06] Fri 01Aug14 14:29:01 - 200 UTF8 set to on

[05] Fri 01Aug14 14:29:01 - OPTS MLST Type;Size;Modify;UNIX.mode;UNIX.owner;UNIX.group;

[06] Fri 01Aug14 14:29:01 - 200 OPTS MLST type;size;modify;UNIX.mode;UNIX.owner;UNIX.group;

[05] Fri 01Aug14 14:29:01 - PWD

[06] Fri 01Aug14 14:29:01 - 257 "/" is the current directory

[13] Fri 01Aug14 14:29:01 - (Action: Synchronize /WfmtJnNw to U:\SatJazNet) - Synchronizing local folder "V:\Import\JazzNetwork" with remote folder "/WfmtJnNw"

[05] Fri 01Aug14 14:29:01 - MLST /WfmtJnNw

[06] Fri 01Aug14 14:29:01 - 250-Start of list for /WfmtJnNw

[06] Fri 01Aug14 14:29:01 - 250-modify=20140801121926;type=dir;UNIX.group=0;UNIX.mode=0755;UNIX.owner=108; /WfmtJnNw

[06] Fri 01Aug14 14:29:01 - 250 End of list

[13] Fri 01Aug14 14:29:01 - (Action: Synchronize /WfmtJnNw to U:\SatJazNet) - Action failed (Last Error Message: Unable to synchronize folders: Could not retrieve additional information about the remote path.  Please make sure the path exists and the logged in user has permissions within the folder.).

[12] Fri 01Aug14 14:29:01 - (Task: Synchronize /WfmtJnNw to U:\SatJazNet) - Execution failed (Last Error Message: Unable to synchronize folders: Could not retrieve additional information about the remote path.  Please make sure the path exists and the logged in user has permissions within the folder.).

[05] Fri 01Aug14 14:29:03 - QUIT

[04] Fri 01Aug14 14:29:03 - The server has unexpectedly closed the connection.

This when successful:

STATUS>    Server supports resume.

COMMAND>    OPTS UTF8 ON

    200 UTF8 set to on

COMMAND>    OPTS MLST Type;Size;Modify;UNIX.mode;UNIX.owner;UNIX.group;

    200 OPTS MLST type;size;modify;UNIX.mode;UNIX.owner;UNIX.group;

COMMAND>    PWD

    257 "/" is the current directory

STATUS>    Receiving: /WfmtJnNw/31351.wav -> \\Prodone\D\Import\JazzNetwork\31351.wav

COMMAND>    TYPE I

    200 Type set to I

COMMAND>    PASV

    227 Entering Passive Mode (107,20,242,177,247,177).

STATUS>    Opening passive mode data connection to 107.20.242.177, port 63409.

COMMAND>    RETR /WfmtJnNw/31351.wav

    150 Opening BINARY mode data connection for /WfmtJnNw/31351.wav (30980476 bytes)

    226 Transfer complete

STATUS>    Transferred 11,539,170 bytes. 3,205.89 KB/sec.

COMMAND>    XCRC "/WfmtJnNw/31350.wav"

    500 XCRC not understood

ERROR>    XCRC command failed. The command may not be supported by this server.

STATUS>    XCRC command checking has been disabled for future transfers using this session.

STATUS>    Received 11,539,170 bytes.

STATUS>    Transfer time: 00:00:03.515.

STATUS>    Receiving: /WfmtJnNw/31352.wav -> \\Prodone\D\Import\JazzNetwork\31352.wav

COMMAND>    PASV

    227 Entering Passive Mode (107,20,242,177,250,204).

STATUS>    Opening passive mode data connection to 107.20.242.177, port 64204.

COMMAND>    RETR /WfmtJnNw/31352.wav

    150 Opening BINARY mode data connection for /WfmtJnNw/31352.wav (3816256 bytes)

    226 Transfer complete

STATUS>    Transferred 3,816,256 bytes. 3,137.05 KB/sec.

STATUS>    Received 3,816,256 bytes.

STATUS>    Transfer time: 00:00:01.188.

STATUS>    Receiving: /WfmtJnNw/31353.wav -> \\Prodone\D\Import\JazzNetwork\31353.wav

COMMAND>    PASV

    227 Entering Passive Mode (107,20,242,177,231,42).

STATUS>    Opening passive mode data connection to 107.20.242.177, port 59178.

COMMAND>    RETR /WfmtJnNw/31353.wav

    150 Opening BINARY mode data connection for /WfmtJnNw/31353.wav (64249380 bytes)

    226 Transfer complete

STATUS>    Transferred 30,980,476 bytes. 3,190.04 KB/sec.

COMMAND>    XCRC "/WfmtJnNw/31351.wav"

    500 XCRC not understood

ERROR>    XCRC command failed. The command may not be supported by this server.

STATUS>    XCRC command checking has been disabled for future transfers using this session.

STATUS>    Received 30,980,476 bytes.

STATUS>    Transfer time: 00:00:09.484.

COMMAND>    QUIT

    221 Goodbye.

    226 Transfer complete

STATUS>    Transferred 64,249,380 bytes. 3,366.07 KB/sec.

STATUS>    Received 64,249,380 bytes.

STATUS>    Transfer time: 00:00:18.640.

COMMAND>    QUIT

    221 Goodbye.

We have created a task that has several actions.  We would like the to get notified when a "Run External Program" task fails.  I have configured the action's "Task Execution Failure" event to notify us when the program fails via email.  However, according to FTP Voyager Scheduler, the task is always successful not matter what exit code we return.  I have tried positive and negative return codes and nothing appears to work.  Any idea how report a "run external program" failure?

Thanks in Advance

Sean

Users transfer date to serv-U server with FTP Voyager.

User do also transfer data to some linux SFTP servers.

We used to have FTP Voyager 15.2.0.15 - everything worked fine.

Since updating to FTP Voyager 16.0.2.0 authentication
with linux SFTP servers fail (connection to Serv-U is still working) It seames that the password is not transferred to the server.

Whithout configuring user and password in server profile: I've been asked for a username - not for the password.

     Log: SSH_MSG_USERAUTH_FAILURE

     /var/log/messages:

Jul  5 07:59:21 chwiitsv042 sshd[29597]: Connection from 10.142.40.230 port 2087

Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: Client protocol version 2.0; client software version FTP Voyager_16.0.2.0

Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: no match: FTP Voyager_16.0.2.0

Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: Enabling compatibility mode for protocol 2.0

Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: Local version string SSH-2.0-OpenSSH_5.1

Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: user zfs-sftp matched group list sftponly at line 143

Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: PAM: initializing for "zfs-sftp"

Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: PAM: setting PAM_RHOST to "10.142.40.230"

Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: PAM: setting PAM_TTY to "ssh"

Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: do_cleanup

Jul  5 07:59:21 chwiitsv042 sshd[29597]: debug1: PAM: cleanup

Anyone an idea what's wrong ?

Thank you very much

Christof

Just wondering if there is documentation or syntax for initiating an FXP transfer in FTP Voyager from the command line? I know how to do it in the GUI, but it would be useful to be able to script it.

We recently replaced our server and had to move FTP Voyager. We took a backup copy of the files as outlined in the article http://www.serv-u.com/kb/1189/how-to-back-up-and-restore-ftp-voyager . We did a new install of FTPVoyager v 16.1.0 and reinstalled the backup files onto the new server.

We have now discovered after much head scratching and lost hours, that the email settings relating to SMTP server, and the sending address (From) are not being correctly maintained. We tried to update the SMTP setttings in the GUI (both in Scheduler and in Voyager) but they are not used when Scheduler runs an Event that requires email. Instead, it appears to use the ones in the FTPVoyagerSettings.Archive file.

In order to change the SMTP server name and the "From" entry we now have to do this by hacking the FTPVoyagerSettings.Archive file rather than via the GUI.

Is this a known bug? Is there anything we can do to get the parameters set in the GUI of Voyager and Scheduler to be retained and used?

Also, whilst asking questions in this area, why are there 2 interfaces for email settings under Tools - one in Options and one in Scheduler options. These seem to be independent as we can put different values in each which are retained between sessions- both of which are ignored(!) in favour of those in FTPVoyagerSettings.Archive file.  I have been unable to track down where the GUI values are actually stored.

A right dog's breakfast.

Barry Sutton.

Hi everyone,

a long time ago I bought a license for FTP Voyager 15.x and I was very happy to hear that from now on it will be free.

So I went ahead to upgrade to the latest version. Unfortunately it still shows evaluation messages but this is already dealt with in another thread.

The bigger problem is that I can't access my saved server profiles any more. It's only possible to import .csv files and I didn't create these files before upgrading.

I uninstalled and tried to download my paid 15.x version in the client area on ftpvoyager.com where it used to be but now it only redirects to the new version.

This is bad because my server list was really huge and I don't want to enter all server details again.

So is there any way to get a copy of an old setup file?

Thanks in advance!

I have setup FTP Voyager with the SMTP settings for gmail to send an email after FTP Scheduler completes a task. I have added the event, send email after task complete, however I do not receive an email.

Any help would be appreciated

Regards

Nick

Hi

I've referred to here by FTP Voyager support.

This is my first time I use FTP Voyager for scheduling file transfer, configuring task was very easy, but I still cannot make it work.

In the task action, I created a new action to download a specific folder (and all files and subfolders inside that folder to my local PC

In action information, I put the (Remote File or Folder) as: /FolderName

Nothing downloaded, and error in the log says:

Execution failed (Last Error Message: Unable to perform file action: Could not retrieve additional information about the source path.  Does the source path exist?).

I changed it to: FolderName (without slash).

Nothing downloaded, and same error in the log.

I then tried: FolderName/*.*

Log says: Execution successfully completed.

But in the local folder, I found it only downloaded files from main folder (No subfolders or files inside them), and some of them with ZERO size !!!!!

Again, I tried: /FolderName/*.*

Log says: Execution successfully completed.

I found that the ZERO size problem has been solved (files downloaded with correct size) but still cannot get the subfolders !

In the forum, I found a link to the older version (ver. 15.2.0.19)

I downloaded and tried it on another PC, It works like a charm, with no errors !

Can anyone here help me to figure out how to make the scheduler download the whole content of remote folder ??

Hi,

Recently got a new computer, and I don't ftp very often, here's the errors I'm receiving, sorry for the length:

FTP Voyager - Version 15.2.0.0

STATUS:>  Connecting to "ftp.j-a-associates.com" on port 21.

          220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------

          220-You are user number 3 of 50 allowed.

          220-Local time is now 16:18. Server port: 21.

          220-This is a private system - No anonymous login

          220-IPv6 connections are also welcome on this server.

          220 You will be disconnected after 15 minutes of inactivity.

STATUS:>  Connected.  Logging into the server

COMMAND:> HOST ftp.j-a-associates.com

          530 You aren't logged in

COMMAND:> USER jaass2

          331 User jaass2 OK. Password required

COMMAND:> PASS *********

          230 OK. Current restricted directory is /

STATUS:>  Login successful

COMMAND:> SYST

          215 UNIX Type: L8

COMMAND:> FEAT

          211-Extensions supported:

           EPRT

           IDLE

           MDTM

           SIZE

           REST STREAM

           MLST type*;size*;sizd*;modify*;UNIX.mode*;UNIX.uid*;UNIX.gid*;unique*;

           MLSD

           AUTH TLS

           PBSZ

           PROT

           ESTA

           PASV

           EPSV

           SPSV

           ESTP

          211 End.

STATUS:>  Server supports resume

COMMAND:> PWD

          257 "/" is your current location

COMMAND:> CWD /

          250 OK. Current directory is /

COMMAND:> OPTS MLST Type;Size;Modify;UNIX.mode;UNIX.owner;UNIX.group;

          200  MLST OPTS type;size;sizd;modify;UNIX.mode;UNIX.uid;UNIX.gid;unique;

COMMAND:> PORT 192,168,1,103,220,112

          200 PORT command successful

COMMAND:> MLSD

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

ERROR:>   Socket error: Unknown socket error (1814)

STATUS:>  Error sending command "MLSD".  Reconnecting (send attempt 2)...

STATUS:>  Connecting to "ftp.j-a-associates.com" on port 21.

          220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------

          220-You are user number 3 of 50 allowed.

          220-Local time is now 16:19. Server port: 21.

          220-This is a private system - No anonymous login

          220-IPv6 connections are also welcome on this server.

          220 You will be disconnected after 15 minutes of inactivity.

STATUS:>  Connected.  Logging into the server

COMMAND:> USER jaass2

          331 User jaass2 OK. Password required

COMMAND:> PASS *********

          230 OK. Current restricted directory is /

STATUS:>  Login successful

COMMAND:> SYST

          215 UNIX Type: L8

STATUS:>  Server supports resume

COMMAND:> CWD /

          250 OK. Current directory is /

STATUS:>  Successful reconnect.  Attempting to resend failed command.

COMMAND:> PORT 192,168,1,103,220,115

          200 PORT command successful

COMMAND:> MLSD

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

ERROR:>   Socket error: Unknown socket error (1814)

STATUS:>  Error sending command "MLSD".  Reconnecting (send attempt 3)...

STATUS:>  Connecting to "ftp.j-a-associates.com" on port 21.

          220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------

          220-You are user number 4 of 50 allowed.

          220-Local time is now 16:20. Server port: 21.

          220-This is a private system - No anonymous login

          220-IPv6 connections are also welcome on this server.

          220 You will be disconnected after 15 minutes of inactivity.

STATUS:>  Connected.  Logging into the server

COMMAND:> USER jaass2

          331 User jaass2 OK. Password required

COMMAND:> PASS *********

          230 OK. Current restricted directory is /

STATUS:>  Login successful

COMMAND:> SYST

          215 UNIX Type: L8

STATUS:>  Server supports resume

COMMAND:> CWD /

          250 OK. Current directory is /

STATUS:>  Successful reconnect.  Attempting to resend failed command.

COMMAND:> PORT 192,168,1,103,220,118

          200 PORT command successful

COMMAND:> MLSD

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

ERROR:>   Socket error: Unknown socket error (1814)

STATUS:>  Error sending command "MLSD".  Reconnecting (send attempt 4)...

COMMAND:> NOOP

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

STATUS:>  Connecting to "ftp.j-a-associates.com" on port 21.

          220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------

          220-You are user number 3 of 50 allowed.

          220-Local time is now 16:22. Server port: 21.

          220-This is a private system - No anonymous login

          220-IPv6 connections are also welcome on this server.

          220 You will be disconnected after 15 minutes of inactivity.

STATUS:>  Connected.  Logging into the server

COMMAND:> USER jaass2

          331 User jaass2 OK. Password required

COMMAND:> PASS *********

          230 OK. Current restricted directory is /

STATUS:>  Login successful

COMMAND:> SYST

          215 UNIX Type: L8

STATUS:>  Server supports resume

COMMAND:> CWD /

          250 OK. Current directory is /

STATUS:>  Successful reconnect.  Attempting to resend failed command.

COMMAND:> PORT 192,168,1,103,220,149

          200 PORT command successful

COMMAND:> MLSD

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

ERROR:>   Socket error: Unknown socket error (1814)

STATUS:>  Error sending command "MLSD".  Reconnecting (send attempt 5)...

STATUS:>  Connecting to "ftp.j-a-associates.com" on port 21.

          220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------

          220-You are user number 3 of 50 allowed.

          220-Local time is now 16:23. Server port: 21.

          220-This is a private system - No anonymous login

          220-IPv6 connections are also welcome on this server.

          220 You will be disconnected after 15 minutes of inactivity.

STATUS:>  Connected.  Logging into the server

COMMAND:> USER jaass2

          331 User jaass2 OK. Password required

COMMAND:> PASS *********

          230 OK. Current restricted directory is /

STATUS:>  Login successful

COMMAND:> SYST

          215 UNIX Type: L8

STATUS:>  Server supports resume

COMMAND:> CWD /

          250 OK. Current directory is /

STATUS:>  Successful reconnect.  Attempting to resend failed command.

COMMAND:> PORT 192,168,1,103,220,153

          200 PORT command successful

COMMAND:> MLSD

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

ERROR:>   Socket error: Unknown socket error (1814)

STATUS:>  Error sending command "MLSD".  Reconnecting (send attempt 6)...

STATUS:>  Connecting to "ftp.j-a-associates.com" on port 21.

          220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------

          220-You are user number 4 of 50 allowed.

          220-Local time is now 16:25. Server port: 21.

          220-This is a private system - No anonymous login

          220-IPv6 connections are also welcome on this server.

          220 You will be disconnected after 15 minutes of inactivity.

STATUS:>  Connected.  Logging into the server

COMMAND:> USER jaass2

          331 User jaass2 OK. Password required

COMMAND:> PASS *********

          230 OK. Current restricted directory is /

STATUS:>  Login successful

COMMAND:> SYST

          215 UNIX Type: L8

STATUS:>  Server supports resume

COMMAND:> CWD /

          250 OK. Current directory is /

STATUS:>  Successful reconnect.  Attempting to resend failed command.

COMMAND:> PORT 192,168,1,103,220,158

          200 PORT command successful

COMMAND:> MLSD

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

ERROR:>   Socket error: Unknown socket error (1814)

STATUS:>  Error sending command "MLSD".  Reconnecting (send attempt 7)...

STATUS:>  Connecting to "ftp.j-a-associates.com" on port 21.

          220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------

          220-You are user number 4 of 50 allowed.

          220-Local time is now 16:26. Server port: 21.

          220-This is a private system - No anonymous login

          220-IPv6 connections are also welcome on this server.

          220 You will be disconnected after 15 minutes of inactivity.

STATUS:>  Connected.  Logging into the server

COMMAND:> USER jaass2

          331 User jaass2 OK. Password required

COMMAND:> PASS *********

          230 OK. Current restricted directory is /

STATUS:>  Login successful

COMMAND:> SYST

COMMAND:> NOOP

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

STATUS:>  Server supports resume

COMMAND:> CWD /

          250 OK. Current directory is /

STATUS:>  Successful reconnect.  Attempting to resend failed command.

COMMAND:> PORT 192,168,1,103,220,160

          200 PORT command successful

COMMAND:> MLSD

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

ERROR:>   Socket error: Unknown socket error (1814)

STATUS:>  Error sending command "MLSD".  Reconnecting (send attempt 8)...

STATUS:>  Connecting to "ftp.j-a-associates.com" on port 21.

          220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------

          220-You are user number 3 of 50 allowed.

          220-Local time is now 16:28. Server port: 21.

          220-This is a private system - No anonymous login

          220-IPv6 connections are also welcome on this server.

          220 You will be disconnected after 15 minutes of inactivity.

STATUS:>  Connected.  Logging into the server

COMMAND:> USER jaass2

          331 User jaass2 OK. Password required

COMMAND:> PASS *********

          230 OK. Current restricted directory is /

STATUS:>  Login successful

COMMAND:> SYST

          215 UNIX Type: L8

STATUS:>  Server supports resume

COMMAND:> CWD /

          250 OK. Current directory is /

STATUS:>  Successful reconnect.  Attempting to resend failed command.

COMMAND:> PORT 192,168,1,103,220,165

          200 PORT command successful

COMMAND:> MLSD

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

ERROR:>   Socket error: Unknown socket error (1814)

STATUS:>  Error sending command "MLSD".  Reconnecting (send attempt 9)...

STATUS:>  Connecting to "ftp.j-a-associates.com" on port 21.

          220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------

          220-You are user number 3 of 50 allowed.

          220-Local time is now 16:29. Server port: 21.

          220-This is a private system - No anonymous login

          220-IPv6 connections are also welcome on this server.

          220 You will be disconnected after 15 minutes of inactivity.

STATUS:>  Connected.  Logging into the server

COMMAND:> USER jaass2

          331 User jaass2 OK. Password required

COMMAND:> PASS *********

          230 OK. Current restricted directory is /

STATUS:>  Login successful

COMMAND:> SYST

          215 UNIX Type: L8

STATUS:>  Server supports resume

COMMAND:> CWD /

          250 OK. Current directory is /

STATUS:>  Successful reconnect.  Attempting to resend failed command.

COMMAND:> PORT 192,168,1,103,220,169

          200 PORT command successful

COMMAND:> MLSD

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

ERROR:>   Socket error: Unknown socket error (1814)

STATUS:>  Error sending command "MLSD".  Reconnecting (send attempt 10)...

COMMAND:> NOOP

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

STATUS:>  Connecting to "ftp.j-a-associates.com" on port 21.

          220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------

          220-You are user number 2 of 50 allowed.

          220-Local time is now 16:31. Server port: 21.

          220-This is a private system - No anonymous login

          220-IPv6 connections are also welcome on this server.

          220 You will be disconnected after 15 minutes of inactivity.

STATUS:>  Connected.  Logging into the server

COMMAND:> USER jaass2

          331 User jaass2 OK. Password required

COMMAND:> PASS *********

          230 OK. Current restricted directory is /

STATUS:>  Login successful

COMMAND:> SYST

          215 UNIX Type: L8

STATUS:>  Server supports resume

COMMAND:> CWD /

          250 OK. Current directory is /

STATUS:>  Successful reconnect.  Attempting to resend failed command.

COMMAND:> PORT 192,168,1,103,220,213

          200 PORT command successful

COMMAND:> MLSD

ERROR:>   Socket error: WSAETIMEDOUT - Connection timed out.  Try using PASV mode (View | Options | Connection) if you receive this error during a LIST, MLSD, or NLST commands. (10060)

ERROR:>   Socket error: Unknown socket error (1814)

STATUS:>  Error sending command "MLSD".  Reconnecting (send attempt 11)...

STATUS:>  Connecting to "ftp.j-a-associates.com" on port 21.

          220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------

          220-You are user number 2 of 50 allowed.

          220-Local time is now 16:32. Server port: 21.

          220-This is a private system - No anonymous login

          220-IPv6 connections are also welcome on this server.

          220 You will be disconnected after 15 minutes of inactivity.

STATUS:>  Connected.  Logging into the server

COMMAND:> USER jaass2

          331 User jaass2 OK. Password required

COMMAND:> PASS *********

          230 OK. Current restricted directory is /

STATUS:>  Login successful

COMMAND:> SYST

          215 UNIX Type: L8

STATUS:>  Server supports resume

COMMAND:> CWD /

          250 OK. Current directory is /

COMMAND:> NOOP

          200 Zzz...

I have several tasks setup to run at different time intervals on a daily basis.

After the time change for Daylight Savings Time on Sunday morning the tasks run as scheduled and then stop and re-start continuously.

I have tried re-starting the service, updating the task scheduler time and re-booting the server all to no avail.

Has anyone else seen this or does anyone have any ideas on how to correct it.

I am on FTP Voyager version 16.0.2.0.

Never had this issue on any previous versions.

Is there a place to download version 15 again????

Hi,

Got FTP-Voyager to work great in command mode using a batch file to initiate file sync to my server from industrial robots to back them up.  Was working great as far as doing the job closing out starting another instance and going to the next robot.

New problem.....

It no longer closes out at the end of the sync.  What option did I change that keeps FTP-Voyager from closing ?  I am using "autoquit=1" in the command line.

Thanks

Stan