Hi,

is it possible to run a schedules\ task remotely with or without CLI?
Is it possible to access FTP Voyager Client on a remote client via Internet browser?

I thank you for any advice.

Kind Regards
FK

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 just found the SolarWinds FTP Voyager Client.  I am looking to use this program for it's FTP scheduling capabilities.

The vendor I will be sending the files to asked if the program has a file in progress extension that it uses when sending files, like .part or .filepart.  They want to filter those extensions so that their processes will ignore the partial uploads until the file has completely uploaded.

Is anyone using the FTP Voyager client?  Does anyone know if it uses a file in progress extension?

Thank you in advance...

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

User do also transfer data to some linux SFTP servers.

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

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

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

     Log: SSH_MSG_USERAUTH_FAILURE

     /var/log/messages:

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

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

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

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

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

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

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

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

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

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

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

Anyone an idea what's wrong ?

Thank you very much

Christof

Hi All. I upgraded by FTP Voyager/Scheduler from v13 to v16. The interface I like along with the stability but I am having issues galore. So I'll post some and see what I get back. The questions below assume it worked fine in v13 and isn't or is doing something different in v16.

1) My downloads from Unix to Windows used ASCII and was fine. Now the CR (carriage returns) are being stripped and I can't figure out why or how to fix it. In global and profile options I have tried all 3 transfer modes. The file is still stripped.

2) My scheduler actions I have just the file to download and the local path I could use the variables for dates and also rename it from there. Now, if I use a variable or rename in that local path line, it creates a folder with the dates variables and put the file in side unchanged. <- driving me crazy.

3) Many jobs were failing saying "path not found" which I learned has to be the absolute path now. Is this true?

Any help with these would be great. I have had to write a bunch of batch files for temporary use until I can figure out how to make Voyager do it [again] like it has been.

Thanks all

My system updated to Windows 10 a few days ago. I went to open Voyager and it will not do anything. It will not FTP any files and it will not open the server side files to access. It just sits and spins. Is this caused from the Windows 10 upgrade or should I look elsewhere? Thanks, Ronald Shackelford.

FTP-Voyager :

Using command line.

Want to upload (to my computer / plant network) files from a Fanuc robot.  The Fanuc robot stores teach pendent files and others files in directories on the robot's internal hard drive.

Using "get=*.*" will not work just as the help files indicate.  Alternate would be to use syncronization.

My question is how to use syncoption command.  The text in the help files are confusing as to which syncoption=1  or syncoption=0 writes to the local hard drive and does not write to the remote hard drive.

It is critical I get it right or I will wipe out the files on a robot and cause massive down time.  Once I figure it out then it's no problem, copy paste in batch file.  (not time to experiment on first time I try it !)

I will be reading all files from the robot and storing into an empty directory on the computer / network as a backup device.  The only time I will write to the robot(s) is when I need to restore a robot on an individual basis like after a power failure and a dead battery in the robot.  I will be writing a batch file with the task of backing up several hundred robots with several hundred files per robot.

(1) Is the syncronization method the best way ? ie: ftp-voyager can only do 100 timed tasks,  I need to have the batch file create and move to new directories under a folder for each robot, and capture all the files.

(2) How does the syncoption command work ie :

• syncoptions: The syncoptions flag specifies how a Synchronization will take place. To determine what value should be used, refer to the list at the bottom of this page. The value here must be a decimal representation of the sum of all applicable hex values. The simplest ones are syncoptions=0 (synchronize a remote folder to a local folder) and syncoptions=1 (synchronize a local folder to a remote folder)
• Synchronize a remote directory to a local directory: "C:\Program Files\RhinoSoft\FTP Voyager\FTPVoyager.exe" profile=YourProfileName autosync=1 syncoptions=1 local=C:\dat\ remote=/dat/ autoquit=1
• Synchronize a local directory to a remote directory: "C:\Program Files\RhinoSoft\FTP Voyager\FTPVoyager.exe" profile=YourProfileName autosync=1 syncoptions=0 local=C:\dat\ remote=/dat/ autoquit=1

The question is which one of these is right ?

Thanks

Stan

Hİ ,

I want to synchronize with ftp voyager scheduler I receive the following error when I am constantly missing or wonder what I'm doing wrong ?

[04] Sun 02Jan14 10:32:32 - Unable to resolve "ftp://ftp.nai.com/" [11004].

[04] Sun 02Jan14 10:32:32 - Connection attempt failed. Retrying in 3 seconds ...

[03] Sun 02Jan14 10:32:36 - Retrying Connection (attempt 9) ...

[03] Sun 02Jan14 10:32:36 - Resolving host "ftp://ftp.nai.com/" ...

[04] Sun 02Jan14 10:32:36 - Unable to resolve "ftp://ftp.nai.com/" [11004].

[12] Sun 02Jan14 10:32:36 - (Task: Daily Backup of 1 Folder) - Execution failed (Last Error Message:).

[12] Sun 02Jan14 10:32:36 - (Task: Daily Backup of 1 Folder) - Next scheduled execution on Friday, January 03, 2014 10:32:00

Pretty sure I have the settings right to get a NEW log file each day, but I'm getting data from days ago in my log file.  Here's my settings - what could be wrong?   Thanks

Image may be NSFW.
Clik here to view.

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?

Do FTP voyager keep a history for the status log?

Hello all,

Voyager has been chugging along for weeks now, with no issues. All of a sudden, the logging behaviour has changed, and I don't understand why. ALL scheduled jobs have logging set like this:

Image may be NSFW.
Clik here to view.

In the past, I would get 1 log file per day that contained all the logs of all the jobs that ran that day: 2014-07-11.txt, 2014-07-12.txt, and so on.

Then all of a sudden, the file 2014-07-14.txt was the last log file created. All the jobs are still being logged, but into the file of the 14th. Why did Voyager suddenly stop creating new log files? There were no updates to the software, the server, the OS, etc. I tried restarting the service, recreating a job, but no luck. Note: I realize the Automatically rotate Log Files is set to Never, but this has been the case from day 1 when it was working. The fact that my logfile name is a variable should force new files to be created. What am I missing?

Al

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

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

I have ensured the following:

1) email settings are proper in the Options area

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

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

4) Tried on two different systems connected to unique networks

Current Scheduler email settings in options:

Server:  smtp.mail.yahoo.com

Port: 465

Use SSL: YES

USE Authentication: YES

Account Name: full email address

Account Password: proper password

Email settings in OPTIONS area are essentially the same.

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

Any suggestions?

Thank you,

brian

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.

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.

We are evaluating FTP Voyager for automating file transfers between sites with SSL. There are two worrisome issues:

1. Email reporting is failing. I am receiving an error in the Scheduler log stating the following:
   1. [04] Wed 31Dec14 13:43:30 - EVENT ERROR: Unable to send message to 'Test_email_Address': Unable to connect to SMTP server  on port 25.
   2. Our SMTP server is functioning with other services from this same server.
   3. I have input the SMTP information into both the FTP Voyager Options and the Scheduler Options.
   4. I have also checked the configuration files called out in another thread here and see our SMTP information correctly.
2. I cannot create Scheduler Site Profiles directly.
   1. I have to create them in the FTP Voyager Site Profile First and then right click and select 'Copy to Scheduler'
   2. If I create them in the Scheduler Site Profile directly, none of the advanced features apply correctly and the profile will not connect to the SSL site.

I believe the two issues may be related.  Issue number 2 is an annoyance but not a show stopper. Issue number 1 on the other hand is preventing me from completing my proof of concept and integration into monitoring.

The scheduler service is running as a domain user with full rights to the server it's running on.

Any assistance would be greatly appreciated. I can provide log files, screen shots, etc. if required.

Thanks,

-Mike

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

Hi, I'm trying to understand how the "Exclude Files Pattern" in Sync Tools works.

I've used RegEx expressions, wildcards and so with no luck.

It works as expected when excluding patter is just one string, in this case all files/folders beginning with that string are omitted.

So first of all, I'd like to understand in general the kind of pattern syntax used by the sync tool, I couldn't figure it out.

What I'm try have is a condition to skip files/folders names that begin/contain/end with a given string...

I'd like to understand how to separate these conditions.

Thanks in advance for any tip

Francesco

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

We've been trying to track down an issue with some scheduled transfers and it turned out that logging to files wasn't enabled on this particular task. I've enabled it and allowed it to run overnight however the log file I expected to see wasn't created. Is there anything that needs to be done after modifying a task to get the changes to take effect?

Also, I opened the Scheduler Log tab in this task about an hour ago and it's still "thinking". What would cause something like this?