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. :-/

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!

Well, I tried.  I really did.  But I'm sick of dealing with this nonsense.  I don't have the time.  I can't wait for a "bug fix" which may never come. 

I have tried the last few weeks to use the new version 16 of FTP Voyager and FTP Scheduler in a production situation and it continues to fail.  I had been very happy with our paid-for version 15 and when I had to provision a new server to perform our FTP synchronization tasks, I assumed that getting the newest version would be the smartest thing to do.  Not only that, but the new version was free! 

However, the myriad critical logic errors in this new version have broken my business' processes and there appears to be no way to submit trouble tickets for the program nor any real tech support (I don't consider a forum "tech support") now that it is "free".  Specifically, I've tried to get two of my own issues resolved, and have been tracking a third:

1. "KEEP ALIVE" when attempting to "move down" a folder with no items in it.
   1. FTP Voyager Scheduler Empty Folder "Move Down" Bug & Possible Work-Around
2. Incorrect "move down" behavior causing data loss.
   1. FTP Voyager Scheduler Move Down File Deletion Behavior
3. Inability to run simultaneous tasks.
   1. Due to One Schedule task stuck & oall thers are in queue

None of these were issues in version 15.  However it pains me, and seeing no actual resolution on my issues, I have to revert a production server and downgrade FTP Voyager to a version that actually works. 

So, with that said, where can I actually download a copy of version 15?  All links available are either dead or point to the v16 download.

We have a job to download a 440MB file every night and this job will frozen once every week causing all the other job afterwards not be executed.

This is giving a big impact on the application level.

We checked our network and is stable

Hello,    

I am currently using FTP Voyager v15.2.0.6.
There are a number of schedules and site profiles associated with this install.

I followed these steps to upgrade:

1. I copied the FTP Voyager Schedule.sch and exported the site profiles.

2. I imported these fields in a clean FTP Voyager 15.2.0.6 install.

3. I ran the upgrade

After running the upgrade the site profiles and schedules are still in working order, however:

- Opening the calender in scheduler causes the scheduler to hang, it just says busy until I manually stop the scheduler service. There is no Windows logging or FTP Voyager logging for this behaviour

- Everything in the scheduled task Window simply states "not scheduled for execution"

Any advice would be appreciated

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...

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.

If I create a new site profile in Voyager I can not see it in Scheduler when I go to set up a new task. How do I get Scheduler to see the profiles created in Voyager? I seem to recall at one time (maybe an earlier version) that there was a way to "send" the profiles to Scheduler....

In scheduler I can see 2 folders - Sites, Personal Sites. But both are empty - even though there are lots of sites defined under these folders in Voyager.

Moreover, when I change site profile details e.g. IP address in Voyager, this is not being picked up by Scheduler which continues to try to connect to the old address.

There seems to be a total breakdown in connection between Voyager and Scheduler.

HELP!

I have a connection set up to a server, all that is fine...

I can send smaller files just fine...

Larger files? It seems that the Command channel times out...

In the header of the Welcome message is a warning of a timeout at 3 minutes of inactivity...

So I dutifully setup a 150 second Keep Alive...

What I see in the log is...

The file (11GB+) sends fine...(Although there seems to be many reconnections during the transfer)

I will see an OPTS MLST command send

followed by a PWD and then a reconnection attempt...

Finally I will see a "Transfered <many> bytes STATUS message... Followed by an XCRC - which seems to receive no response after maybe 30 seconds...

Then another PWD...

Then an ERROR> Server has unexpectedly closed the connection...

And we start again....

Ideas?

Hello, I've scoured this site as well as the web looking for an answer to my Voyager email challenges.

I really like the program and in fact it seems to work very well for what I'm doing; however, I cannot make the email alerts function at all.

I have ensured the following:

1) email settings are proper in the Options area

2) email setting match the Option email settings in the "Scheduler Options" area

3) Tried both a gmail account and yahoo.  The gmail refuses to work always timing out regardless.  The yahoo account never errors out but then emails are never received, which is confusing.

4) Tried on two different systems connected to unique networks

Current Scheduler email settings in options:

Server:  smtp.mail.yahoo.com

Port: 465

Use SSL: YES

USE Authentication: YES

Account Name: full email address

Account Password: proper password

Email settings in OPTIONS area are essentially the same.

EVENT setup in the TASK:  Execution START as well as the EVENT SCHEDULE area.

Any suggestions?

Thank you,

brian

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

Continually getting the following message after a connection is created from FTP Voyager:

SSL accept failed on FTP data channel - The connection will be aborted

Using FTP over TLS - explicit

Works from FileZilla for example to the same host with the same credentials.

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?

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 ??

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.

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.

We are wondering about distributing FTP Voyager to members of certain teams within our company. However, for security we do not want to allow scheduling for most users. We try to keep all recurring jobs off workstations and on dedicated machines. Is it possible to install FTP Voyager without the scheduling component?

Do FTP voyager keep a history for the status log?

i have a task i want to delete from the scheduler. It starts automatically and never ends. I click the stop button and it doesn' t do anything. Is there a way to clear the list manually?

How do you remove a site from Schedulers site list?

I learned how to add them from this forum but can't seem to get rid of some old one no longer used or needed.