Hi, encountered the error below when I am trying to create a key pair in FTP Voyager. Anyone can advise on this?

Thank you.

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 want to use FTP Voyager to upload data on a regular schedule from remote sites to my FTP server.  The application checks all of the boxes for what I need it to do: Upload all files in a folder, do some XCRC/XMD5/XSHA1, and then delete the local files after successful upload.  My problem is that the scheduled task seems to never complete sometimes and we stop receiving files.

The Internet connections for most of our locations frequently drop.  It seems this might have something to do with the problem.  My oldest installation has been running reliably since July and has a solid connection.  The scheduler hangs most frequently on sites with the worst connectivity issues.

I have implemented a klugey work-around by scheduling a task that restarts the Voyager scheduler service.  This keeps the problem from manifesting and we receive our files.

I set the following scheduler options:

• connection timeout = 90
• connection retries = 9
• connection delay = 3
• transfer send timeout = 90
• transfer idle timeout = 5
• file transfer upload file tries = 10

Scheduled task creation:

1. I create a scheduled task that runs every 15 minutes.
2. Add an action to run an external program.  This executes a batch file that moves files into a staging folder for the FTP transfer.
3. Add a second action to synchronize remote folders.  This moves the files up to our FTP server.
   1. I add an event to this action that runs a batch file after upload.  The batch file is there to delete the uploaded file and is passed, "$LocalPath", as an argument.

This setup works perfectly well in my lab and at the site with the consistent Internet connection.  Other locations have been seen to work for days and even weeks, but eventually the scheduled task hangs until the scheduler service is restarted.  Any help would be greatly appreciated.

Trying to use the FTP Voyager as a backup utility for my dedicated server.

Runs flawlessly until it hits the last folder. Thought for a while it was hanging in the middle of the backup, but created a empty folder after the last folder it had been backing up - and it hung on that folder.

It reaches the point where it should just disconnect from the remote server, with a complete back up. But it does not disconnect and repeating a KEEP ALIVE line.

Any suggestions on how to get it to disconnect and complete the job?

I had a Task that was configured incorrectly that caused it to run for several hours straight. During this time there where other tasks that where scheduled to run but did not. It was not until I manualy stoped the long running task did the other tasks start. The log file generated the following messages:

The log file states the following for the task that did not execute when it was scheduled:

"Task is scheduled for execution when current tasks complete. This task's position is number 1."

Is there a way to schedule tasks to run concurrently?

Log file attached.

Evidently this is a widespread problem according to the posts and Google searches.

I'm using version 16.1.0.0 and most scheduled 'Move Up' tasks just hang.

The log files show the Quit command multiple times but the process just keeps running, doing nothing except preventing other tasks from running.

The only way to fix it is to cancel the task, then start execution over.

Is there any planned resolution for this?

I've been trying to figure it out for several weeks, trying all sorts of different things, but obviously it's a program bug.

This is taking me several hours a week to log into client computers, clean up the task process and restart.

I'll give it until 9/1/14 then will look for an alternate product that works.

And I'll be sure to post my experience wherever I can so others don't have to deal with the same issue.

We are using the scheduler to move files to a customer ftp server. The process just moves files, nothing else. Currently the task will run but hang, when we check the customer ftp server we can see files are transferred. But there is always zero length files. I assume these are the placeholder of the file to be transferred. Process will just hang after 5 or 6 files and the files that are transferred are not deleting from home directory. The files are only 2kb each so I can't imagine file size being the problem.

Is there a queue size limit on number of files that can be transferred? We have sometimes up to a thousand files that will need to be moved. Also does the process only delete after it has completed? We have seen it complete once or twice with about 40 files, but that is so random we can't call it an actual successful test.

Thanks

Jim

ftp Voyager Scheduler 16.1.0.0 is set to run many scheduled uploads, but on many of these uploads it appears to hang after completion, the log records the task as completed with the last lines reading:

Sent xxxxx bytes

Transfer time: 00:00:02.587

QUIT

221

but in the Scheduler task tab the task appears to be still running, this blocks all other tasks from starting and a user must manually abort the running task.

Anyone any ideas what might be happening here?

Hi,

I installed the FTP Voyager software on a server on a 2nd site. Everything has been configured on site 1 and is working as intended. I configured everything the same way on site 2nd site and the task never ends. I tried a backup and a sync with and without other tasks (emails on success/failure), nothing works. It does the job as insrtucted but the task never ends meaning the next day, the backup will never run.

How can I fix this?

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!

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.

Hello

I am trying to connect to a site using FTP over TLS (explicit) with port 21.

I am able to connect with no problems using other FTP clients but I cannot with FTP Voyager.

I am able to connect using standard FTP.

I am also able to connect with SSH which I didnt know I could.

My password is correct.  Again, I can connect with many other clients using the same settings.

Could it have anything with FTP Voyager thinking the server certificate is insecure?

ANy setting to allow insecure certificates to try that?

ANy help is apprecoated.

Thanks

This is the log:

STATUS> Resolving host "ftp.mysite.net"...

STATUS> Connecting to "111.111.111.58" on port 21.

STATUS> Connected to 111.111.111.58:21 from 192.168.1.127:51112.

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

220-You are user number 1 of 50 allowed.

220-Local time is now 10: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.

COMMAND> AUTH TLS

234 AUTH TLS OK.

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

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 am trying to run Execute an ftp voyager scheduled sync manually,

This scheduled event syncs files from Pershing to a network location on our server

It looks like it works and ftp voyager scheduler does not spit out an error neither do I receive an email notification that sync has failed which I set up yesterday in the Event section of Task properties.

but when I go to the network share the files look like they have not been synced.

Passwords for the connections were changed on Saturday the 10th of November but since then I have entered the new passwords in FTP Voyager.

so I checked the logs below.

03] Wed 14Nov18 09:34:55 - Resolving host "clientftp.bnymellon.com"...

[03] Wed 14Nov18 09:34:55 - Connecting to "170.61.238.34" on port 22.

@

[03] Wed 14Nov18 09:34:55 - Connected to 170.61.238.34:22 from 10.0.3.7:51906.

[03] Wed 14Nov18 09:34:55 - Negotiating SSH2 session with server...

[03] Wed 14Nov18 09:34:55 - Client Identification: SSH-2.0-FTP Voyager_16.2.0.328

[03] Wed 14Nov18 09:34:55 - Server Identification: SSH-2.0-Serv-U_15.0.0.0

[03] Wed 14Nov18 09:34:55 - Initializing key exchange process...

[03] Wed 14Nov18 09:34:55 - Selected key exchange algorithm: diffie-hellman-group1-sha1

[03] Wed 14Nov18 09:34:55 - Host Key Fingerprint: 7A:D3:AB:F6:04:85:42:2A:04:60:4E:7B:CA:48:EA:C3

[03] Wed 14Nov18 09:34:55 - Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

[03] Wed 14Nov18 09:34:55 - Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib

[03] Wed 14Nov18 09:34:55 - Selected public key protocol: ssh-dss

[03] Wed 14Nov18 09:34:55 - Key exchange process successfully completed.

[07] Wed 14Nov18 09:34:55 - SSH_MSG_SERVICE_REQUEST: service: ssh-userauth

[08] Wed 14Nov18 09:34:55 - SSH_MSG_SERVICE_ACCEPT: service accepted

[03] Wed 14Nov18 09:34:55 - Querying server for supported authentication methods

[07] Wed 14Nov18 09:34:55 - SSH_MSG_USERAUTH_REQUEST: user: qg5n8a1; service: ssh-connection; type: none

[08] Wed 14Nov18 09:34:55 - SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey

[03] Wed 14Nov18 09:34:55 - Supported authentication methods: password, publickey

[07] Wed 14Nov18 09:34:55 - SSH_MSG_USERAUTH_REQUEST: user: qg5n8a1; service: ssh-connection; type: password

[04] Wed 14Nov18 09:34:55 - Password not accepted.

[04] Wed 14Nov18 09:34:55 - Unable to login.

[04] Wed 14Nov18 09:34:55 - Connection attempt failed. Retrying in 3 seconds...

[07] Wed 14Nov18 09:34:55 - SSH_MSG_DISCONNECT: reason code 11; description: Password not accepted.

[04] Wed 14Nov18 09:34:55 - The server has unexpectedly closed the connection.

[04] Wed 14Nov18 09:34:55 - Connection attempt failed. Retrying in 3 seconds...

Please help.

Hi, encountered the error below when I am trying to create a key pair in FTP Voyager. Anyone can advise on this?

Thank you.

I have multiple users getting this crash in FTP Voyager:

Faulting application name: FTP Voyager.exe, version: 16.2.0.328, time stamp: 0x542c320b

Faulting module name: SHELL32.dll, version: 10.0.17134.1, time stamp: 0x75c40783

Exception code: 0xc0000005

Fault offset: 0x0000000000053dc4

Faulting process id: 0x1f04

Faulting application start time: 0x01d480400b074d8c

Faulting application path: C:\Program Files\RhinoSoft\FTP Voyager\FTP Voyager.exe

Faulting module path: C:\windows\System32\SHELL32.dll

Report Id: 23c7bee2-035f-4439-aa16-24dd8572198b

Faulting package full name:

Faulting package-relative application ID:

The users are on Win 10x64 ver 1803 build 17134.

Voyager launches without an issue. Once in it, users can connect to different site profiles. As they are browsing folders, the application randomly crashes, usually while waiting for a  folder to load. It happens on multiple folders and does not always crash.

Does anyone have an idea what may be causing it?

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

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

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

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

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

A right dog's breakfast.

Barry Sutton.

Hi

I am able to upload files to a remote destimation but there is

a problem downloading.

For example, when I donwload a csv, it downloads the

file name and extension of .csv but the contents is blank and is 0KB in

size.

Do you know what would be causing this please?

Best regards

Dan

Hello... I want add environment variables (like %computername%) into body mail on "Events" Then, when some ftp voyager task fail, it will shows thats environment on the email. Thanks!

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