I am using FTP voyager 16.1.0.0 mainly because of the powerful scheduling features (running on windows 2008 r2 standard edition 64 bit).

I have my own internal processes that back up a load of databases and their document folders every evening and creates a set of compressed files with the day of the week in the file name.

I then created 7 scheduled tasks in voyager that each run very early in the morning the day after backups are due to complete as show here...

Then in the actions of each of these tasks all i do is add a synchronize action that has an Ignore filter of "Not Matching wildcard" with "*monday*.*" so that only that days files will attempt to sync between the live server and the backup server, like this....

The problem is, that every other day FTP voyager seems to forget the filter and will use the default "starting with" filter rather than the "Not Matching wildcard" and because nothing in my folder starts with that it will sync a massive folder and spend days trying to do.

The loss of the setting seems to be triggered when the action is happening but can't recreate it, all I know is if I go to the server, see the schedulers tray icon flashing then I know when I go in there is will still be trying to sync after 2 days and the setting has reverted again. If I visit the scheduler when it isn't having trouble then all the settings will be fine.

Has anyone seen this behaviour before please, I was really hopeful when I found this system but will have to give up on it soon if I don't find a fix.

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

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

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

Can someone help? thanks.

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

echo.found %%G

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

Echo uploaded %%G successfully

Echo.

)

Echo.

Echo completed ...

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

I'm trying to run and external program from within an action. The Program to Run: C:\Windows\notepad.exe

From what I see in the Task Log, it appears everything worked.

[13] Mon 09Sep13 12:49:49 - (Action: Open Notepad) - Running external program: C:\Windows\notepad.exe

[13] Mon 09Sep13 12:49:49 - (Action: Open Notepad) - Action successfully completed.

[12] Mon 09Sep13 12:49:49 - (Task: Open Notepad) - Execution successfully completed.

[05] Mon 09Sep13 12:49:53 - QUIT

Except nothing happened.

I am using Windows 7, 64-bit.

BTW, if I put in an invalid path (C:\Windowsx\notepad.exe), the Task Log reports

[12] Mon 09Sep13 13:20:50 - (Task: Open Notepad) - Execution failed (Last Error Message: (0x2) The system cannot find the file specified.).

So it appears finding notepad.exe isn't the issue.

Is there a way i can have a schedule setup to send a file and move the file once sent to a SENT folder. ive used other Clients before where this is possible but im struggling to find an option to do this,

we have a folder full of files that need to be sent out over FTP, once the files have been sent the files will need to be moved to the SENT folder as a backup.

many thanks in advanced and hope there is something that can be done

Another strange issue with FTP Voyager v16. I have a site profile that is using 21, very simple. The credentials land me in my home dirctory. If I try and connect it keeps failing over and over because it is trying a CWD a directory named exactly where I landed, in my home directory. Funny thing is I am using the profile in Schedule and works just fine. I've deleted it and recreated it and the same thing happens. I used another FTP program to connect with exact same credentials and it connects just fine. I'm really regreting upgrading to this version from v13. The application was very buggy and crashed but I was able to get the job done without all the little things that changed. Snippet of the error. It happens over and over and over until I stop it. And of course I removed the actual names.

                       257 "//serverA/shareB" is current directory.

COMMAND>             CWD /severA/shareB

                       550  /serverA/shareB: No such file or directory.

ERROR>          Unable to change to folder "/serverA/shareB".

..regret

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

We are trying to upgrade our FTP Voyager from 11.1 to 16.1.  I've been working through all the kinks, but have gotten stuck on running the 16.1 scheduler as a service and being able to access in house network shares (not remote ones).  The PC is Windows 7 Pro 64 bit.  I've done everything in KB article #1156 and the recommendations at the bottom in article #1679.  They both talk about setting the service to run as a network account that has access to the shared resources.  I've tried various domain admin accounts that I know have permissions to the shares and security permissions to the folders, but when I am editing or creating a schedule and try to setup an action, I am only given local drives to pick from when I click the browse button for the "Local File or Folder" field on the Action Properties page.  If I don't run the scheduler as a service, clicking the browse button gives me a list of local drives and all my mapped drives.  And I tried running the service with the same user id and password that the computer was logged in with when the scheduler was run in stand alone mode and showed me the mapped drives, but it still only showed me local drives when ran as a service.  I've tried all this with UAC on and off, with no change.  I don't know what to try next.  Please help.

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!

Using Ver. 16.1.0.0, manual Synchronization works fine, but when scheduled using Schedule Management Console Synchronization fails, here are the logs.

Thanks,

B

This when it fails

[03] Fri 01Aug14 14:29:01 - Server supports resume.

[05] Fri 01Aug14 14:29:01 - OPTS UTF8 ON

[06] Fri 01Aug14 14:29:01 - 200 UTF8 set to on

[05] Fri 01Aug14 14:29:01 - OPTS MLST Type;Size;Modify;UNIX.mode;UNIX.owner;UNIX.group;

[06] Fri 01Aug14 14:29:01 - 200 OPTS MLST type;size;modify;UNIX.mode;UNIX.owner;UNIX.group;

[05] Fri 01Aug14 14:29:01 - PWD

[06] Fri 01Aug14 14:29:01 - 257 "/" is the current directory

[13] Fri 01Aug14 14:29:01 - (Action: Synchronize /WfmtJnNw to U:\SatJazNet) - Synchronizing local folder "V:\Import\JazzNetwork" with remote folder "/WfmtJnNw"

[05] Fri 01Aug14 14:29:01 - MLST /WfmtJnNw

[06] Fri 01Aug14 14:29:01 - 250-Start of list for /WfmtJnNw

[06] Fri 01Aug14 14:29:01 - 250-modify=20140801121926;type=dir;UNIX.group=0;UNIX.mode=0755;UNIX.owner=108; /WfmtJnNw

[06] Fri 01Aug14 14:29:01 - 250 End of list

[13] Fri 01Aug14 14:29:01 - (Action: Synchronize /WfmtJnNw to U:\SatJazNet) - Action failed (Last Error Message: Unable to synchronize folders: Could not retrieve additional information about the remote path.  Please make sure the path exists and the logged in user has permissions within the folder.).

[12] Fri 01Aug14 14:29:01 - (Task: Synchronize /WfmtJnNw to U:\SatJazNet) - Execution failed (Last Error Message: Unable to synchronize folders: Could not retrieve additional information about the remote path.  Please make sure the path exists and the logged in user has permissions within the folder.).

[05] Fri 01Aug14 14:29:03 - QUIT

[04] Fri 01Aug14 14:29:03 - The server has unexpectedly closed the connection.

This when successful:

STATUS>    Server supports resume.

COMMAND>    OPTS UTF8 ON

    200 UTF8 set to on

COMMAND>    OPTS MLST Type;Size;Modify;UNIX.mode;UNIX.owner;UNIX.group;

    200 OPTS MLST type;size;modify;UNIX.mode;UNIX.owner;UNIX.group;

COMMAND>    PWD

    257 "/" is the current directory

STATUS>    Receiving: /WfmtJnNw/31351.wav -> \\Prodone\D\Import\JazzNetwork\31351.wav

COMMAND>    TYPE I

    200 Type set to I

COMMAND>    PASV

    227 Entering Passive Mode (107,20,242,177,247,177).

STATUS>    Opening passive mode data connection to 107.20.242.177, port 63409.

COMMAND>    RETR /WfmtJnNw/31351.wav

    150 Opening BINARY mode data connection for /WfmtJnNw/31351.wav (30980476 bytes)

    226 Transfer complete

STATUS>    Transferred 11,539,170 bytes. 3,205.89 KB/sec.

COMMAND>    XCRC "/WfmtJnNw/31350.wav"

    500 XCRC not understood

ERROR>    XCRC command failed. The command may not be supported by this server.

STATUS>    XCRC command checking has been disabled for future transfers using this session.

STATUS>    Received 11,539,170 bytes.

STATUS>    Transfer time: 00:00:03.515.

STATUS>    Receiving: /WfmtJnNw/31352.wav -> \\Prodone\D\Import\JazzNetwork\31352.wav

COMMAND>    PASV

    227 Entering Passive Mode (107,20,242,177,250,204).

STATUS>    Opening passive mode data connection to 107.20.242.177, port 64204.

COMMAND>    RETR /WfmtJnNw/31352.wav

    150 Opening BINARY mode data connection for /WfmtJnNw/31352.wav (3816256 bytes)

    226 Transfer complete

STATUS>    Transferred 3,816,256 bytes. 3,137.05 KB/sec.

STATUS>    Received 3,816,256 bytes.

STATUS>    Transfer time: 00:00:01.188.

STATUS>    Receiving: /WfmtJnNw/31353.wav -> \\Prodone\D\Import\JazzNetwork\31353.wav

COMMAND>    PASV

    227 Entering Passive Mode (107,20,242,177,231,42).

STATUS>    Opening passive mode data connection to 107.20.242.177, port 59178.

COMMAND>    RETR /WfmtJnNw/31353.wav

    150 Opening BINARY mode data connection for /WfmtJnNw/31353.wav (64249380 bytes)

    226 Transfer complete

STATUS>    Transferred 30,980,476 bytes. 3,190.04 KB/sec.

COMMAND>    XCRC "/WfmtJnNw/31351.wav"

    500 XCRC not understood

ERROR>    XCRC command failed. The command may not be supported by this server.

STATUS>    XCRC command checking has been disabled for future transfers using this session.

STATUS>    Received 30,980,476 bytes.

STATUS>    Transfer time: 00:00:09.484.

COMMAND>    QUIT

    221 Goodbye.

    226 Transfer complete

STATUS>    Transferred 64,249,380 bytes. 3,366.07 KB/sec.

STATUS>    Received 64,249,380 bytes.

STATUS>    Transfer time: 00:00:18.640.

COMMAND>    QUIT

    221 Goodbye.

Something has happened with our installation of Voyager to cause the scheduler service to become unstable. I'm trying to determine the safest way to perform a repair on the software to try and get it back up and running.

We have the following error in the windows event logs:

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

Faulting module name: MSVCR100.dll, version: 10.0.40219.325, time stamp: 0x4df2bcac

Exception code: 0xc0000417

Fault offset: 0x0000000000070468

Faulting process id: 0xbec

Faulting application start time: 0x01d04b96d28e7566

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

Faulting module path: C:\Program Files\RhinoSoft\FTP Voyager\MSVCR100.dll

Report Id: 11a095ee-b78a-11e4-80d6-005056a8624c

Faulting package full name:

Faulting package-relative application ID:

Any suggestions? We have quite a few profiles that we don't want to have to re-create here so I'm hoping there is a repair process rather than a clean re install.

Thanks

I have a problem with FTP Voyager 16.2.0.328, i have some mapped network drives in WIndows Server 2012, i started the time sheduler, but i canot select in the time sheduler a network drive, in the normale Voyage i can select the network drive.

I hope someone can help me or say the answer for this troubleshooting.

Hi guys,

We are using FTP voyager for our ftp services and I am very new to this client.

I am planning to migrate our ftp sites to new AWS environment and when I tried to connect using Site Profiles Manager for an SFTP client, I am getting an error like this

The server has unexpectedly closed the connection.

Would you please help me to find a solution for it?

This is the log file info

Thanks

Suj

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

what can we be doing wrong?

I have successfully uploaded with other clients but there scheduling is lacking so that's why i want to use ftp voyager.

We have noticed that Voyager does not successfully copy all files from our Serv-U server to a local share when writes are happening simultaneously at the server. Most of the files get copied just fine and all files show up in the Voyager log as copied. We are running Voyager Version 16.0.1.1 on a Windows 7 Enterprise OS. The system is a Virtual Server.

We are positive that if we are not writing files to the Serv-U server at the same time as the Voyager schedular is trying to process files, everything comes down just fine. It  only seems to be an issue during a write to the Serv-U system.

Thanks!

Mike -  Skagit IT

Hi guys,

I purchased this product 7 years ago and have used many a version of this product. This program has worked flawlessly for quite sometime now until just recently. I added a new SFTP personal site and am able to connect with it no problem. I went into the scheduler and would like to add a new task. There is a requirement to pick one of your sites to associate the task with, but my new personal site doesn't show up. I didn't get any support from case number 616750 as their excuse is that "We cannot support you, since it is now a free product" I bet the guys at Rhinosoft would be quite ashamed at hearing that their paying customers are receiving service like that nowadays. Anyways has anyone encountered this issue with the scheduler?

Thanks in advance for any help.

In FTP Voyager I create a site profile under “Tool – Scheduler Site Profiles”. I’m able to connect to this profile and manually upload and manage documents. I created a Task in Scheduler to sync the remote folder using the profile I create. When executed I get the following error “Execution failed (Last Error Message: )”.

Why am I getting the error in Scheduler when I don’t making a direct connection?

Snippet from log:

[03] Wed 21May14 12:02:57 - Server supports resume.

[05] Wed 21May14 12:02:57 - OPTS UTF8 ON

[06] Wed 21May14 12:02:57 - 200 OPTS UTF8 command successful - UTF8 encoding now ON.

[05] Wed 21May14 12:02:57 - PWD

[06] Wed 21May14 12:02:57 - 257 "/" is current directory.

[13] Wed 21May14 12:02:57 - (Action: "C:\pdcloud01 hold\Trade Show\CSV File\Idatix" to "/") - Synchronizing remote folder "/" with local folder "C:\pdcloud01 hold\Trade Show\CSV File\Idatix"

[05] Wed 21May14 12:02:57 - CWD /

[06] Wed 21May14 12:02:57 - 250 CWD command successful.

[05] Wed 21May14 12:02:57 - PORT 47,23,21,53,245,30

[06] Wed 21May14 12:02:57 - 200 PORT command successful.

[05] Wed 21May14 12:02:57 - LIST

[06] Wed 21May14 12:02:57 - 150 Opening ASCII mode data connection.

[06] Wed 21May14 12:03:19 - 550

[13] Wed 21May14 12:03:19 - (Action: "C:\pdcloud01 hold\Trade Show\CSV File\Idatix" to "/") - Action failed (Last Error Message: ).

[12] Wed 21May14 12:03:19 - (Task: fd test) - Execution failed (Last Error Message: ).

[12] Wed 21May14 12:03:19 - (Task: fd test) - Next scheduled execution on Wednesday, May 21, 2014 12:12:56

[05] Wed 21May14 12:03:19 - QUIT

[06] Wed 21May14 12:03:19 - 221 Goodbye