Hi,

I want to FTP synch every week to a synology box for backups.  I use windows task scheudler to start the vpn to my client, launch FTP voyager.

I have a few questions:

1. is the remote direct of "/" acceptable in FTP Voyager Scheduler?  It appears to work then fails saying it needs admin priviledges (login is admin on the synology box)- logs are not sayign what happened
2. Do I need FTP Voyager running when using FTP Voyager scheduler?- appears not except for email settings/notification
3. is there a paid version?- I am reading posts where <build 16 was way better.  Since I am using this for business and FTP really is a simple protocol, i want support at my fingertips

FTP Voyager is recognizing the file I’m trying to upload as a directory for some reason. Transferring to remote location fails with message xxxx.ARMOH is a directory. (Remote side does not accept directories) however xxxx.ARMOH is a file. Anyway to inform Voyager of this and only send files.

Question regarding the FTP Voyager Scheduler.  I have it set so that every 30 minutes kicks off a job and will transfer files if some exist in the designated directory.

Is it possible to set this up so that it looks in a directory, say every 5 minutes, and if files exist then it proceeds to connect and transfer the files?

Hello,

I really need your help to solve this issue.

We are using FTP Voyager V16.2.0.328 to schedule different tasks to send messages to our partners.

The problem is that sometimes, the tasks are frozen. It keeps trying to connect but do nothing, and as it doesn't send an issue mail.

In the log, the action stay  : Connected

To solve it, we just interrupt the task in order to run the other tasks.

Is there a solution to kill the task after X min, or to send a mail when the task stay connected more than X Min ?

Thanks a lot for your help.

I Use FTP Voyager Scheduler for auto upload/download file to FTP server

I have around 10 FTP task with scheduler , 1 day all task scheduler stop running and when I go to log file , I see that 1 task keep running forever  so causes the other sessions all are in queue.

My question is do you have any mechanism /solution so that can try to stop a session if it run for example more than 5 minutes.

Or we have any monitor so we know which task schedule frozen , tks

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

Hi,

I'm trying to use FTP Voyager Scheduler to upload files on the FTP. But if the connection was disconnected during the files transfer, the scheduler was hang (still showing executing, but from the log, you can see that nothing is running).

Is it possible to solve this problem? Please kindly advice. Thank you.

Hi,

We have a scheduled task that should upload a file to a remote location via FTP over SSL or TLS. This was working fine with version 15 but not now with version 16. The upload works sometimes but most of the time it doesn't.

We really need this to work or else a downgrade must be done. So any ideas or questions will be appreciated.

Kind regards,

Peter Nilsson

STATUS> Resolving host "ftps.xxxxx.xx"...

STATUS> Connecting to "nnn.nnn.nnn.nnn" on port 21.

STATUS> Connected to nnn.nnn.nnn.nnn:21 from nnn.nn.n.nnn:64626.

220-FTP 10:12:22 on 2016-03-15.

220 Connection will close if idle for more than 5 minutes.

COMMAND> AUTH TLS

234 Security environment established - ready for negotiation

STATUS> SSL connection established. All transactions are now secure.

STATUS> Encryption cipher: 256 bit AES; Version: TLSv1/SSLv3.

STATUS> Connected. Logging in to the server.

COMMAND> USER xyz

331 Send password please.

COMMAND> PASS ***

230 xyz is logged on.  Working directory is "/remotefolder1/remotefolder2/out".

STATUS> Login successful.

COMMAND> SYST

215 UNIX is the operating system of this server. FTP Server is running on z/OS.

COMMAND> FEAT

211- Extensions supported

SIZE

MDTM

AUTH TLS

PBSZ

PROT

211 End

COMMAND> REST 100

504 Restart requires Block or Compressed transfer mode.

STATUS> Server supports resume.

COMMAND> PBSZ 0

200 Protection buffer size accepted

COMMAND> PROT P

200 Data connection protection set to private

COMMAND> PWD

257 "/remotefolder1/remotefolder2/out" is the HFS working directory.

COMMAND> CWD /remotefolder1/remotefolder2/in

250 HFS directory /remotefolder1/remotefolder2/in is the current working directory

COMMAND> PASV

227 Entering Passive Mode (nnn,nnn,nnn,nnn,nnn,nn)

STATUS> Opening passive mode data connection to nnn.nnn.nnn.nnn, port 60734.

STATUS> Negotiating SSL connection with server...

COMMAND> LIST /remotefolder1/remotefolder2/in/File123.txt

550 LIST cmd failed : ls: FSUM6785 File or directory "/remotefolder1/remotefolder2/in/File123.txt" is not found

STATUS> Sending: \\localserver\localfolder1\localfolder2\out\File123.txt -> /remotefolder1/remotefolder2/in/File123.txt

COMMAND> TYPE A

ERROR> SSL Accept failed on FTP data channel. The connection will be aborted.

STATUS> Resolving host "ftps.xxxxx.xx"...

STATUS> Connecting to "nnn.nnn.nnn.nnn" on port 21.

STATUS> Connected to nnn.nnn.nnn.nnn:21 from nnn.nn.n.nnn:64630.

220-FTP 10:12:25 on 2016-03-15.

220 Connection will close if idle for more than 5 minutes.

COMMAND> AUTH TLS

234 Security environment established - ready for negotiation

STATUS> SSL connection established. All transactions are now secure.

STATUS> Encryption cipher: 256 bit AES; Version: TLSv1/SSLv3.

STATUS> Connected. Logging in to the server.

COMMAND> USER xyz

331 Send password please.

COMMAND> PASS ***

230 xyz is logged on.  Working directory is "/remotefolder1/remotefolder2/out".

STATUS> Login successful.

COMMAND> SYST

215 UNIX is the operating system of this server. FTP Server is running on z/OS.

COMMAND> FEAT

211- Extensions supported

SIZE

MDTM

AUTH TLS

PBSZ

PROT

211 End

COMMAND> REST 100

504 Restart requires Block or Compressed transfer mode.

STATUS> Server supports resume.

COMMAND> PBSZ 0

200 Protection buffer size accepted

COMMAND> PROT P

200 Data connection protection set to private

COMMAND> PWD

257 "/remotefolder1/remotefolder2/out" is the HFS working directory.

COMMAND> QUIT

221 Quit command received. Goodbye.

We need to send a document via FTP over TLS (Explicit) using TLS 1.1.  Does FTP Voyager 16.1 support that?  If so, how do I get my site profile to use that?

Thanks

Hello! I'm using FTP Voyager 16.2.0.328 on Windows 2012 R2. I have a few tasks created when daylight saving was on. They are scheduled to execute every 5-30 minutes. When daylight saving ended these tasks now executes every 1 hour plus the original schedule e.g. every 1 hour and 30 minutes instead of every 30 minutes. Copy the existing tasks to new tasks didn't help, I had to re-create the tasks to get rid of this.

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

I'm running this script on my PC1 with FTP Voyager version 16.2 but it does just open FTP voyager and DOES NOTHING.  No file transfer at all.

I checked and I do see 2 zip files inside d:\temp\ folder.  However if I take this same script and execute on another PC and it work fine.  This PC has same FTP voyager version and same configuration as PC1.

Can someone help? thanks.

FOR %%G in (d:\temp\*.zip) do (

echo.found %%G

"C:\Program Files\RhinoSoft\FTP Voyager\FTP Voyager.exe" profile="Art_Test_FTPserver" put=%%G remote="/" logfile=NAR_upload.log -nostartupwizard -nosplash autoquit=1

Echo uploaded %%G successfully

Echo.

)

Echo.

Echo completed ...

Just recently our server that is running FTP Voyager, started experiencing some odd things with the scheduler.  The tray icon will show up and seem like it is running.  Btw, we're running 16.2.0.328.  However, when I click on the system tray and try to start the management console, it never comes up.  I can kill the processes and try again, but it doesn't change anything.  I can see the tray and scheduler processes running in the task manager.  Is there any other way to get the management console for the scheduler to come up?  Any help would be greatly appreciated.

Our server is Windows Server 2012 R2 Standard.

Thanks

Greg

I am getting this error and I don't know what the problem is. 

SSH Disconnect Error: no more authentication methods available.

We are using Serv-U on the back-end and FTP Voyager on the front end.

Regular password based connections work fine.

As soon as I create a private / public key and bind it to the user (on both sides), then the authentication will not work. 

Here is the log.

Perhaps I have to disable password authentication before public key authenication will work?

STATUS>    Resolving host "abc.myspecialsite.com"...

STATUS>    Connecting to "65.212.176.194" on port 22.

STATUS>    Connected to 65.212.176.194:22 from 10.0.0.25:58052.

STATUS>    Negotiating SSH2 session with server...

STATUS>    Client Identification: SSH-2.0-FTP Voyager_16.2.0.328

STATUS>    Server Identification: SSH-2.0-2.0

STATUS>    Initializing key exchange process...

STATUS>    Selected key exchange algorithm: diffie-hellman-group1-sha1

STATUS>    Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99

STATUS>    Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

STATUS>    Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

STATUS>    Selected public key protocol: ssh-rsa

STATUS>    Key exchange process successfully completed.

COMMAND>    SSH_MSG_SERVICE_REQUEST: service: ssh-userauth

    SSH_MSG_SERVICE_ACCEPT: service accepted

STATUS>    Querying server for supported authentication methods

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none

    SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey

STATUS>    Supported authentication methods: password, publickey

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey

    SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey

    SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey

ERROR>    SSH Disconnect Error: no more authentication methods available.

ERROR>    Unable to login.

ERROR>    Connection attempt failed.  Retrying in 3 seconds...

COMMAND>    SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.

ERROR>    The server has unexpectedly closed the connection.

ERROR>    Connection attempt failed.  Retrying in 3 seconds...

STATUS>    Retrying Connection (attempt 2)...

STATUS>    Resolving host "abc.myspecialsite.com"...

STATUS>    Connecting to "65.212.176.194" on port 22.

STATUS>    Connected to 65.212.176.194:22 from 10.0.0.25:58054.

STATUS>    Negotiating SSH2 session with server...

STATUS>    Client Identification: SSH-2.0-FTP Voyager_16.2.0.328

STATUS>    Server Identification: SSH-2.0-2.0

STATUS>    Initializing key exchange process...

STATUS>    Selected key exchange algorithm: diffie-hellman-group1-sha1

STATUS>    Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99

STATUS>    Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

STATUS>    Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

STATUS>    Selected public key protocol: ssh-rsa

STATUS>    Key exchange process successfully completed.

COMMAND>    SSH_MSG_SERVICE_REQUEST: service: ssh-userauth

    SSH_MSG_SERVICE_ACCEPT: service accepted

STATUS>    Querying server for supported authentication methods

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none

    SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey

STATUS>    Supported authentication methods: password, publickey

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey

    SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey

    SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey

ERROR>    SSH Disconnect Error: no more authentication methods available.

ERROR>    Unable to login.

ERROR>    Connection attempt failed.  Retrying in 3 seconds...

COMMAND>    SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.

ERROR>    The server has unexpectedly closed the connection.

ERROR>    Connection attempt failed.  Retrying in 3 seconds...

STATUS>    Retrying Connection (attempt 3)...

STATUS>    Resolving host "abc.myspecialsite.com"...

STATUS>    Connecting to "65.212.176.194" on port 22.

STATUS>    Connected to 65.212.176.194:22 from 10.0.0.25:58056.

STATUS>    Negotiating SSH2 session with server...

STATUS>    Client Identification: SSH-2.0-FTP Voyager_16.2.0.328

STATUS>    Server Identification: SSH-2.0-2.0

STATUS>    Initializing key exchange process...

STATUS>    Selected key exchange algorithm: diffie-hellman-group1-sha1

STATUS>    Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99

STATUS>    Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

STATUS>    Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

STATUS>    Selected public key protocol: ssh-rsa

STATUS>    Key exchange process successfully completed.

COMMAND>    SSH_MSG_SERVICE_REQUEST: service: ssh-userauth

    SSH_MSG_SERVICE_ACCEPT: service accepted

STATUS>    Querying server for supported authentication methods

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none

    SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey

STATUS>    Supported authentication methods: password, publickey

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey

    SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey

    SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey

ERROR>    SSH Disconnect Error: no more authentication methods available.

ERROR>    Unable to login.

ERROR>    Connection attempt failed.  Retrying in 3 seconds...

COMMAND>    SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.

ERROR>    The server has unexpectedly closed the connection.

ERROR>    Connection attempt failed.  Retrying in 3 seconds...

STATUS>    Retrying Connection (attempt 4)...

STATUS>    Resolving host "abc.myspecialsite.com"...

STATUS>    Connecting to "65.212.176.194" on port 22.

STATUS>    Connected to 65.212.176.194:22 from 10.0.0.25:58058.

STATUS>    Negotiating SSH2 session with server...

STATUS>    Client Identification: SSH-2.0-FTP Voyager_16.2.0.328

STATUS>    Server Identification: SSH-2.0-2.0

STATUS>    Initializing key exchange process...

STATUS>    Selected key exchange algorithm: diffie-hellman-group1-sha1

STATUS>    Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99

STATUS>    Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

STATUS>    Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

STATUS>    Selected public key protocol: ssh-rsa

STATUS>    Key exchange process successfully completed.

COMMAND>    SSH_MSG_SERVICE_REQUEST: service: ssh-userauth

    SSH_MSG_SERVICE_ACCEPT: service accepted

STATUS>    Querying server for supported authentication methods

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none

    SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey

STATUS>    Supported authentication methods: password, publickey

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey

    SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey

    SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey

ERROR>    SSH Disconnect Error: no more authentication methods available.

ERROR>    Unable to login.

ERROR>    Connection attempt failed.  Retrying in 3 seconds...

COMMAND>    SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.

ERROR>    The server has unexpectedly closed the connection.

ERROR>    Connection attempt failed.  Retrying in 3 seconds...

STATUS>    Retrying Connection (attempt 5)...

STATUS>    Resolving host "abc.myspecialsite.com"...

STATUS>    Connecting to "65.212.176.194" on port 22.

STATUS>    Connected to 65.212.176.194:22 from 10.0.0.25:58060.

STATUS>    Negotiating SSH2 session with server...

STATUS>    Client Identification: SSH-2.0-FTP Voyager_16.2.0.328

STATUS>    Server Identification: SSH-2.0-2.0

STATUS>    Initializing key exchange process...

STATUS>    Selected key exchange algorithm: diffie-hellman-group1-sha1

STATUS>    Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99

STATUS>    Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

STATUS>    Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

STATUS>    Selected public key protocol: ssh-rsa

STATUS>    Key exchange process successfully completed.

COMMAND>    SSH_MSG_SERVICE_REQUEST: service: ssh-userauth

    SSH_MSG_SERVICE_ACCEPT: service accepted

STATUS>    Querying server for supported authentication methods

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none

    SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey

STATUS>    Supported authentication methods: password, publickey

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey

    SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey

    SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey

ERROR>    SSH Disconnect Error: no more authentication methods available.

ERROR>    Unable to login.

ERROR>    Connection attempt failed.  Retrying in 3 seconds...

COMMAND>    SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.

ERROR>    The server has unexpectedly closed the connection.

ERROR>    Connection attempt failed.  Retrying in 3 seconds...

STATUS>    Retrying Connection (attempt 6)...

STATUS>    Resolving host "abc.myspecialsite.com"...

STATUS>    Connecting to "65.212.176.194" on port 22.

STATUS>    Connected to 65.212.176.194:22 from 10.0.0.25:58061.

STATUS>    Negotiating SSH2 session with server...

STATUS>    Client Identification: SSH-2.0-FTP Voyager_16.2.0.328

STATUS>    Server Identification: SSH-2.0-2.0

STATUS>    Initializing key exchange process...

STATUS>    Selected key exchange algorithm: diffie-hellman-group1-sha1

STATUS>    Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99

STATUS>    Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

STATUS>    Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

STATUS>    Selected public key protocol: ssh-rsa

STATUS>    Key exchange process successfully completed.

COMMAND>    SSH_MSG_SERVICE_REQUEST: service: ssh-userauth

    SSH_MSG_SERVICE_ACCEPT: service accepted

STATUS>    Querying server for supported authentication methods

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none

    SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey

STATUS>    Supported authentication methods: password, publickey

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey

    SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted

COMMAND>    SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey

    SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey

ERROR>    SSH Disconnect Error: no more authentication methods available.

ERROR>    Unable to login.

ERROR>    Connection attempt failed.  Retrying in 3 seconds...

COMMAND>    SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.

ERROR>    The server has unexpectedly closed the connection.

ERROR>    Connection attempt failed.  Retrying in 3 seconds...

STATUS>    Retrying Connection (attempt 7)...

STATUS>    Resolving host "abc.myspecialsite.com"...

STATUS>    Connecting to "65.212.176.194" on port 22.

STATUS>    Connected to 65.212.176.194:22 from 10.0.0.25:58064.

STATUS>    Negotiating SSH2 session with server...

STATUS>    Client Identification: SSH-2.0-FTP Voyager_16.2.0.328

ERROR>    The server has unexpectedly closed the connection.

ERROR>    Could not establish a connection to MFT-AIM.

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

I have set up the SMTP for the scheduler to use the smtp details for Office 365 which uses port 587. When the event attempts to run, I get an error saying

Unable to send message to xxxxxxxxxxx Unable to connect to SMTP server on port 25

1) Why is this failing?

2) Why is it saying it is using port 25 when I have told it to use port 587?

Thanks

We have FTP Voyager 16.1.0.0 installed on a Windows 2008 R2 server. We have two automatic uploads scheduled to occur weekly (FTP Voyager establishes a connection to the destination and then moves and .CSV files from a particular directory to the destination). Once the file has been successfully moved, an email alert is generated and delivered internally.

This configuration has been working fine, until Daylight savings time began on march 9th.

Now, when the scheduled job runs, it executes continuously for an entire hour; because we receive an email alert when it runs, we know it executes about 2,600 times.

e.g. a scheduled task that should execute one time at 0420 on tuesday is now executing once every few seconds for an hour.

There is a line item on the release notes for 16.1.0.0 (The version we have) which states

FTP client release notes for FTP Voyager.

• Corrected a Scheduler bug where tasks created when daylight savings time is off and scheduled to run daily or at a custom interval would repeatedly run for an hour after their scheduled execution time when daylight savings time resumed.

which is exactly what we're experiencing - is this a known issue / was the bug not actually corrected?

Thanks!

I'm trying to used the command line interface of FTP Voyager and the 'profile' switch is working to connect me to the correct site, but the 'put' is not.  The site opens and I don't see any attempt to upload the file.

Below is the generated command line:

D:\Program Files\RhinoSoft\FTP Voyager\FTP Voyager.exe profile=NOR1 put=T:\Cognos\Exports\NOR1\AFFSHB20140417.tab

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.

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