Is it possible to set up a task schedule to execute every hour between 11 AM and 3 PM everyday of the week?
↧
Execute a task every x minutes/hours every day between two times?
↧
FTP Voyager 550 failed to change directory error
Hello All,
Please I have an issue trying to synchronize a particular folder from a remote location (MyBookLive) to a local machine (Windows Server 2008).
Other folders synchronize ok, but this particular folder keeps giving me this error.
"
"
↧
↧
FTP Voyager Scheduler not working (Ver. 16.0.2.0)
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 ??
↧
FTP-Voyager in command line mode.
Hi,
Got FTP-Voyager to work great in command mode using a batch file to initiate file sync to my server from industrial robots to back them up. Was working great as far as doing the job closing out starting another instance and going to the next robot.
New problem.....
It no longer closes out at the end of the sync. What option did I change that keeps FTP-Voyager from closing ? I am using "autoquit=1" in the command line.
Thanks
Stan
↧
FTP VOYAGER CRASHING
i have the latest FTP VOYAGER and in the last few weeks it has started giving me problems. Every time I upload something it does the upload and then crashes so if I need to upload something else I have to start again. I have no I idea why and it is really annoying. Has anyone else come across this or can suggest why and how to stop it happening please?
Thanks
↧
↧
Back up FTP Voyager Scheduler Settings
Hello
Is there anyway to backup all the Scheduler settings?
(Site Profiles and Tasks)
↧
Where are FTP Voyager Scheduler actions stored on disk?
When I create an action, where is the configuration file stored on my hard drive? I am interested in programmatically modifying some of the action settings in the FTP Voyager Scheduler. For instance, if I put FTP Voyager on 5 computers and need to make a small modification to their settings, I would prefer not to have to go to all 5 computers to make this change. Instead, I could send an updated configuration file to each computer when I send out updates and the new settings will take affect, after perhaps requiring a reboot of the service.
Is this possible? Are FTP Voyager Scheduler settings or actions written to some .config/xml/.ini or other type of file?
Thanks!
↧
FTP Voyager Scheduler hangs when connecting to F5
I'm setting up the FTP Voyager Scheduler to download backup files from our F5's. It works on some, with this log message:
[12] Tue 13Oct15 12:05:04 - (Task: f5-internal-01_backup) - Execution successfully completed.
[07] Tue 13Oct15 12:05:07 - SSH_MSG_DISCONNECT: reason code 11; description: Disconnection initiated by user.
But fails on 4 out of 6 with this log message:
[07] Tue 13Oct15 14:05:48 - SSH_MSG_DISCONNECT: reason code 11; description: Disconnection initiated by user.
[13] Tue 13Oct15 14:07:24 - (Action: "/var/local/ucs" to "C:\SFTP_Root\f5-internal-03") - Action was aborted.
[12] Tue 13Oct15 14:07:24 - (Task: f5-internal-03_backup) - Execution was aborted.
[07] Tue 13Oct15 14:07:24 - SSH_MSG_DISCONNECT: reason code 11; description: Disconnection initiated by user.
The last message is from having to cancel the task, as it just sits at "Executing". The only difference is the F5 OS version, the ones that work are 11.2.0 and the ones that fail are 11.6.0, anyone see this before?
↧
FTP Voyager Scheduler Hangs
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
↧
↧
V16.2.0.328: Daylight saving bug still present, WTF?
As a veeery long time licensed FTP Voyager user since 2000 (And I have a V9.0.1.4 version still running on W2K without any troubles for years) my first choice for a new setup on W7 was FTP Voyager again. Of course.
But now I am very disappointed.
Until last friday every scheduled task (Nine tasks every day) everything was allright, but with the last weekend here in Germany the summer time came into game. And guess what, since Monday every task runs again and again for an hour and floods my mail account with failure mails.
I have tasks running once a day generating a single log for every day, before DST such a log had a size of 12kb, since monday they are growing up to 7,5megs and have about 397000 lines. For transferring ONE file!
Ok, it's a SFTP setup with key file authentication and this produces a lot of auth lines, but for sure not that much.
Hey Solar Winds, whats going on with your quality control? What to do now, re-generate every job and do that again every spring?
↧
FTP Voyager Scheduler hang when connection to FTP was disconnected accidently
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.
↧
Running multiple profiles in ftp voyager
HI,
Why can't ftp voyager run multiple task in scheduler ?
I created some profiles to synchronize from different location. However only one task runs at a time. The remaining task are scheduled.
Is it possible to run multiple profiles together.
Help please.
Regards
Redoctober.
↧
FTP Voyager Scheduler Hangs - Service Restart Required
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:
- I create a scheduled task that runs every 15 minutes.
- Add an action to run an external program. This executes a batch file that moves files into a staging folder for the FTP transfer.
- Add a second action to synchronize remote folders. This moves the files up to our FTP server.
- 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.
↧
↧
Scheduler Service flapping on and off
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
↧
Question on FTP Voyager use with Serv-U
Hello,
We are trying to set up FTP Voyager for use with Serv-U. The scenario is this: we want to have a user set up in Serv-U so that when they log in and upload a file FTP Voyager is invoked via command line to move a file to another system (lileky the file that was uploaded). The problem is that we cannot seem to get FTP Voyager to actually work as intended even removing Serv-U from the equation.
According to KB article #1140 this is the command line to invoke FTP Voyager:
"C:\Program Files\RhinoSoft\FTP Voyager\FTPVoyager.exe" profile="Personal Site.My Site" put=C:\file.txt
I get Voyager to come up and it does log into the profile just fine because we see the user's remote folder structure however the "put" command does not work, regardless of how it is invoked. We have tried a number of command line structures including how it is actually invocked in Serv-U which looked like this in the logs:
Event: FILE_UPLOAD (mtintdev file upload); Type: EXECUTE; Path "C:\Program Files\RhinoSoft\FTP Voyager\FTP Voyager.exe"; Parameters "profile="TESTDEVORA" put="Q:\DEV\files\testuser\testfile.txt"
(In the user event we actually use these parameters: profile="TESTDEVORA" put=$LocalPathName so that it goes to the file that was just uploaded but that's beside the point right now.)
If this is put in the command window:
"C:\Program Files\RhinoSoft\FTP Voyager\FTP Voyager.exe" profile=TESTDEVORA put=Q:\DEV\files\testuser\testfile.txt
Voyager loads, we get the remote folder but nothign else happens. It's as if the "put" command is not recognized. Anyone else have this issue? Suggestions?
↧
FTP Voyager - Scheduler problem
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!
↧
FTP Voyager Scheduler Move Down File Deletion Behavior
So the Move Down functionality in FTP Voyager Scheduler is not consistent with what one would typically call a file move operation. Previously, in version 15 of FTP Voyager, a Move Down operation behaved like this:
- Get list of all files at destination.
- Copy remote file to local destination.
- Delete remote file.
- Go to next file on list.
- Continue until list is empty.
Now, however, version 16 behaves like this:
- Get list of all files at destination.
- Copy remote file to local destination.
- Go to next file.
- Continue until list generated at step 1 is complete.
- Delete all remote files at destination, regardless of what was contained in list generated at step 1.
Effectively it is just the Download and Delete Remote Path commands chained together. This is a big problem for my automation, as I cannot guarantee that the folder won't have new files created in it during download operations #2-4, which will then ultimately get deleted by step #5.
So long story short, can the behavior be reverted to the v15 style of move?
↧
↧
Trouble sending large files to a Pure-FTPd Server
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?
↧
FTP Voyager Scheduler and Network Shares
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.
↧
ftp voyager 16 - problem with large files?
Im just testing the free voyager 16 on default settings. With large files over several GB the speed either drops down to almost zero, or the transfer just restarts.
Tried transfering one image backup, at one point it had 15 minutes left, the next time it had started the transfer all over again.
Any ideas if this is a bug or some setting that could be adjusted?
↧