Hello

I’m trying to run FTP Voyager from the command line like so:call "C:\Program Files\RhinoSoft\FTP Voyager\FTP Voyager.exe" profile=ZFTP autosync=1 syncoptions=0 local=C:\zsm2web\ remote=/ZSMDOC/ autoquit=1

This works if the remote folder is empty.

I want  to overwrite the existing files based on the timestamp of the files in the local folder or delete the files if they dont exist in de local folder.

Can anyone give me a working example using :

syncoptions List

•         SyncRemote = 0x0000

•         SyncLocal = 0x0001

• IgnoreCase = 0x0002

• CompareSize = 0x0004

• CompareTime = 0x0008

• IncludeDirs = 0x0010

• DontDelete = 0x0020

• OverwriteConfirmations = 0x0040

• DeleteConfirmations = 0x0080

• RemoteIgnoreNewer = 0x0100

• RemoteIgnoreOlder = 0x0200

• LocalIgnoreNewer = 0x0400

• LocalIgnoreOlder = 0x0800

• MinimizeStatusDialogs = 0x1000

• QueueErrorMessages = 0x2000

• IgnoreSymbolicLinks = 0x4000

  Not sure how i should add this to the command line so a complete working example woulde be appreciated

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.

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.

I have a situation where I will FTP a file to a folder and then need to move it to another folder on the remote server. I have seen the automatic rename function and have tried testing this on my own network but it does not appear that I can rename a file where I can specify a file path in the automatic rename function. I would have to do this automatically through the scheduler.

Hi, I keep getting an error "The operation cannot be performed" while trying to save an action. The screenshot shows FTP Voyager in the background with the connection open from the "Scheduler Site Profile Manager" and I have full access to the remote site... any help would be appreciated!

(Windows server 2003 sp2, FTP Voyager Ver 16.2.0.328)

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

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.

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

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

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?

The FTP voyager doesn't delete the file after a move up.

When I perform a move task and the a delete task, the server moves and deletes perfectly the file. But I want that both actions can be handled with the move up.

I use the FTP voyager version 16.1.0.0

03] Wed 12Apr17 13:44:16 - Server supports resume.

[05] Wed 12Apr17 13:44:16 - CLNT FTP Voyager 16.1.0.0

[05] Wed 12Apr17 13:44:16 - STOR 20170412112901_20170412112858_af_5_4.pdf

[06] Wed 12Apr17 13:44:16 - 200 Don't care

[05] Wed 12Apr17 13:44:16 - OPTS UTF8 ON

[06] Wed 12Apr17 13:44:16 - 150 Opening data channel for file upload to server of "/Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste/20170412112901_20170412112858_af_5_4.pdf"

[06] Wed 12Apr17 13:44:17 - 202 UTF8 mode is always enabled. No need to send this command.

[05] Wed 12Apr17 13:44:17 - PWD

[06] Wed 12Apr17 13:44:17 - 257 "/" is current directory.

[05] Wed 12Apr17 13:44:17 - CWD /Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste

[06] Wed 12Apr17 13:44:17 - 250 CWD successful. "/Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste" is current directory.

[05] Wed 12Apr17 13:44:17 - MLST /Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste/20170412113759_20170412113758_ENI_0.pdf

[06] Wed 12Apr17 13:44:17 - 250-Listing /Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste/20170412113759_20170412113758_ENI_0.pdf

[06] Wed 12Apr17 13:44:17 -  type=file;size=174798;modify=20170412114416; /Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste/20170412113759_20170412113758_ENI_0.pdf

[06] Wed 12Apr17 13:44:17 - 250 End

[05] Wed 12Apr17 13:44:17 - MLST /Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste/20170412113759_20170412113758_ENI_0 (2).pdf

[06] Wed 12Apr17 13:44:17 - 550 File or directory not found.

[03] Wed 12Apr17 13:44:17 - Sending: C:\ADM\Test2\BE0659837055_AF_Aankoopfacturen_BrasserieJuste\20170412113759_20170412113758_ENI_0.pdf -> /Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste/20170412113759_20170412113758_ENI_0.pdf

[05] Wed 12Apr17 13:44:17 - TYPE I

[06] Wed 12Apr17 13:44:17 - 200 Type set to I

[05] Wed 12Apr17 13:44:17 - PASV

[06] Wed 12Apr17 13:44:17 - 227 Entering Passive Mode (136,144,129,18,195,72)

[03] Wed 12Apr17 13:44:17 - Opening passive mode data connection to 136.144.129.18, port 49992.

[05] Wed 12Apr17 13:44:17 - STOR 20170412113759_20170412113758_ENI_0.pdf

[06] Wed 12Apr17 13:44:17 - 150 Opening data channel for file upload to server of "/Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste/20170412113759_20170412113758_ENI_0.pdf"

[06] Wed 12Apr17 13:44:17 - 226 Successfully transferred "/Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste/20170412113759_20170412113758_ENI_0.pdf"

[03] Wed 12Apr17 13:44:17 - Transferred 174 798 bytes. 641,73 KB/sec.

[05] Wed 12Apr17 13:44:17 - XCRC "/Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste/20170412113759_20170412113758_ENI_0.pdf"

[04] Wed 12Apr17 13:44:17 - The server has unexpectedly closed the connection.

[06] Wed 12Apr17 13:44:17 - 226 Successfully transferred "/Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste/20170412112901_20170412112858_af_5_4.pdf"

[03] Wed 12Apr17 13:44:17 - Transferred 1 207 004 bytes. 1 796,82 KB/sec.

[05] Wed 12Apr17 13:44:17 - XCRC "/Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste/20170412112901_20170412112858_af_5_4.pdf"

[04] Wed 12Apr17 13:44:17 - The server has unexpectedly closed the connection.

[03] Wed 12Apr17 13:44:17 - Connecting to "136.144.129.18" on port 21.

[03] Wed 12Apr17 13:44:17 - Connected to 136.144.129.18:21 from 192.168.149.242:53539.

[06] Wed 12Apr17 13:44:17 - 220-FileZilla Server 0.9.60 beta

[06] Wed 12Apr17 13:44:17 - 220-written by Tim Kosse (tim.kosse@filezilla-project.org)

[06] Wed 12Apr17 13:44:17 - 220 Please visit https://filezilla-project.org/

[03] Wed 12Apr17 13:44:17 - Connected. Logging in to the server.

[05] Wed 12Apr17 13:44:17 - USER certifisc2

[06] Wed 12Apr17 13:44:17 - 331 Password required for certifisc2

[05] Wed 12Apr17 13:44:17 - PASS ***

[06] Wed 12Apr17 13:44:17 - 230 Logged on

[03] Wed 12Apr17 13:44:17 - Login successful.

[05] Wed 12Apr17 13:44:17 - SYST

[06] Wed 12Apr17 13:44:17 - 215 UNIX emulated by FileZilla

[05] Wed 12Apr17 13:44:17 - FEAT

[06] Wed 12Apr17 13:44:17 - 211-Features:

[06] Wed 12Apr17 13:44:17 -  MDTM

[06] Wed 12Apr17 13:44:17 -  REST STREAM

[06] Wed 12Apr17 13:44:17 -  SIZE

[06] Wed 12Apr17 13:44:17 -  MLST type*;size*;modify*;

[06] Wed 12Apr17 13:44:17 -  MLSD

[06] Wed 12Apr17 13:44:17 -  UTF8

[06] Wed 12Apr17 13:44:17 -  CLNT

[06] Wed 12Apr17 13:44:17 -  MFMT

[06] Wed 12Apr17 13:44:17 -  EPSV

[06] Wed 12Apr17 13:44:17 -  EPRT

[06] Wed 12Apr17 13:44:17 - 211 End

[03] Wed 12Apr17 13:44:17 - Server supports resume.

[05] Wed 12Apr17 13:44:17 - CLNT FTP Voyager 16.1.0.0

[06] Wed 12Apr17 13:44:17 - 200 Don't care

[05] Wed 12Apr17 13:44:17 - OPTS UTF8 ON

[06] Wed 12Apr17 13:44:17 - 202 UTF8 mode is always enabled. No need to send this command.

[05] Wed 12Apr17 13:44:17 - PWD

[06] Wed 12Apr17 13:44:17 - 257 "/" is current directory.

[13] Wed 12Apr17 13:44:17 - (Action: "C:\ADM\Test2\*" to "/Test") - Action successfully completed.

[12] Wed 12Apr17 13:44:17 - (Task: test) - Execution successfully completed.

[05] Wed 12Apr17 13:44:24 - QUIT

[06] Wed 12Apr17 13:44:24 - 221 Goodbye

Freeze Log

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

Hello

I’m trying to run FTP Voyager from the command line like so:call "C:\Program Files\RhinoSoft\FTP Voyager\FTP Voyager.exe" profile=ZFTP autosync=1 syncoptions=0 local=C:\zsm2web\ remote=/ZSMDOC/ autoquit=1

This works if the remote folder is empty.

I want  to overwrite the existing files based on the timestamp of the files in the local folder or delete the files if they dont exist in de local folder.

Can anyone give me a working example using :

syncoptions List

•         SyncRemote = 0x0000

•         SyncLocal = 0x0001

• IgnoreCase = 0x0002

• CompareSize = 0x0004

• CompareTime = 0x0008

• IncludeDirs = 0x0010

• DontDelete = 0x0020

• OverwriteConfirmations = 0x0040

• DeleteConfirmations = 0x0080

• RemoteIgnoreNewer = 0x0100

• RemoteIgnoreOlder = 0x0200

• LocalIgnoreNewer = 0x0400

• LocalIgnoreOlder = 0x0800

• MinimizeStatusDialogs = 0x1000

• QueueErrorMessages = 0x2000

• IgnoreSymbolicLinks = 0x4000

  Not sure how i should add this to the command line so a complete working example woulde be appreciated

Hello,

I've been using FTP Voyager for a little over a year now. My event email notifications have always worked. All of the sudden about a month ago the email notifications come form Voyager have been sporadic and then not at all. I don't see anything wrong with my SMTP server seeing as everything else is coming through it (such as my web filter, firewall and other server notifications). It is only notifications from FTP Voyager. Is this a known error?

Thanks.

Hello,

I hope to get some help with this problem. I try to use FTP Voyager on a Windows server, to automate some crucial tasks.

The schedule is entered, looks fine. It should synchronize a FTP-folder to a local folder, and it downloads all files (.txt files) correctly, except the ones that are really important, the Excel-files. That is, they are downloaded, but remain empty (0 Kb). When I try to do the same thin within FTP Voyager, i.e. Not with the Scheduler, everything runs fine. What could be the problem? It drives me mad.

Thanks in advance!

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.

Hello,

I'm having trouble with this configuration. . .

Windows Server 2008R2 + Voyager 16.0.2.0 + FTP over TLS (implicit) + PASV + connection to Serv-U v6.4

I get this error is in the log:

COMMAND> PASV

227 Entering Passive Mode (70,89,1xx,1xx,7,209)     <== Note, this is the Serv-U IP address.

"ERROR> The home directory specified for this account on the remote server is not accessible. Please contact your system administrator for further assistance."

Things I've tested. . .

This works great (home directory displays, but not for Serv-U):

Windows Server 2008R2 + Voyager 16.0.2.0 + SFTP + PASV + connection to non-Serv-U servers

. . .and this works (home directory displays on Serv-U but using an older version of Voyager + Win7 instead of 2008R2):

Windows7 + Voyager 16.0.1.1 + FTP over TLS (implicit) + PASV + connection to Serv-U v6.4

I'm not using the Scheduler "as service" to do this testing - just the Voyager UI. I'm thinking I should try loading 16.0.1.1 on the 2008R2 server but hesitate because I'm afraid it could screw up the Scheduler that is running other jobs.

Any one have similar experience?

Thanks.

Doug

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!

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.

Since I can't sync the remote site to my local disk, I use Download feature instead of Sync.

FTP Voyager Scheduler time out

It works as expected and can download the files as pre-scheduled.

But I check the files and logs, It download ALL THE TIME. Again and again to overlap existed files. Can I set the default action of download, or Can I set the tools ONLY download new uploading or newer files ?

Regards