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.
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?
I have been going crazy attempting to upload files to another (Linux) server and I am getting errors.
once I figured out how to get the sites to show up when using the scheduler, i used the export and import rather then re-create accounts.
a users guide with examples would be really great! i can find any such thing.
so the issue i am see is this... I can connect using the browser and upload files with no issues. when i use the scheduler, I have to specfiy the local and remote directories. this is where things get interesting. I am placed in a home directory on the remote side, so for the remote side I just use / and for the local side i click on the folder icon and navigate to the folder E:\folder\folder1 and I would assume that everything in folder1 would be uploaded. Wrong! it tries to create the remotefolder2 and dose not have permissions and so it fails. why is it trying to create folders? in the help man, it says that the directory listed in the local and remote will grab everything in that folder and says nothging about trying to create that folder. I just want to move files in that local folder1 to the remotefolder2.
the Actions I have tried so far is as follows:
Upload: "E:\localfolder\localfolder1" to "/"
Upload: "E:\localfolder\localfolder1" to "/remotefolder/remotefolder1/remotefolder2"
Upload: "E:\localfolder\localfolder1\*.*" to "/"
any trailing "/" or "\" are removed when you hit save.
when I add the /remotefolder/remotefolder1/remotefolder2 to the remote folder location, the error logs show it attempts to create remote directories remotefolder/remotefolder1/remotefolder2
I have changed the site profile advanced options \ file transfer \ transfer mode to Binary.
here is the thing i don't understand. I can connect using the browser and see the remote site, and i can transfer files to and delete on the remote end with no issues at all and the logs are much smaller. only when trying to use the scheduler is where things go goofy.
I am trying to connect to a vendor's MFT to upload and download files using. I can connect using FileZilla but not FTP Voyager. Here is a screenshot of the log showing the error I am receiving. Any suggestions would be greatly appreciated. Thanks.
I am helping a local accounting firm migrate their infrastructure to a virtual cloud environment where they have multiple virtual desktops and one virtual server with their data on it. Prior to moving their data, one of their daily duties was to scan documents into PDF's and drop them on a network share in a particular folder for their customer(s) for data retention. Now that they are using a cloud, this process becomes more challenging. My thought was to use the Voyager FTP solution along with Voyager FTP Scheduler to take files scanned on a desktop and saved locally on a folder and sync it with their virtual server via an FTP connection. If I create a folder on the virtual server called "tempscans" and kick off the task on Voyager Scheduler, it will save this file to the correct folder. Now I am wondering if this utility can merge files in existing folders when it does it's scheduled sync? My thought was to create a local folder on each local desktop with just the folder structure that has the names of their customers only minus any files. That way, when they scan a document into PDF, they can perform a "Save As" option to the respected folder and hopefully, when the scheduled sync kicks off, it will just merge that new file in with the existing and in the existing folder.
I've been a long-time user of FTP Voyager, well before SW bought up RhinoSoft. I even paid for it too, back in those days. However, lately I upgraded to the new version, and found out that hey! It's free now! Cool!
However, all was not sunshine and roses. I too have run into the FTP Voyager Scheduler empty folder bug, wherein you perform a "Move Down" command against an empty folder and it simply sits there. In my case, it performs KEEP ALIVE tasks to hold the connection open. Critically, because this task is still executing, it will not execute any of the other scheduled tasks. See below for a log output.
[03] Fri 05Dec14 14:15:49 - Getting "real path" name to keep connection alive (KEEP ALIVE)
I see that this is a known issue here on the forums, and that there are supposidly "bug fix requests" or something to handle it. However, I have a problem with this NOW.
I believe I found a simple work around. I chained a file upload to the destination folder first, uploading a single 1-byte file to the destination, and THEN performing the full folder move down.
This will always cause the remote folder to have something in it, and for then the task to complete successfully. I then set up my local-side automation to ignore that file, and things were working.
Not exactly elegant, but it's working for now. :-/
We need to send a document via FTP over TLS (Explicit) using TLS 1.1. Does FTP Voyager 16.1 support that? If so, how do I get my site profile to use that?
The FTP voyager doesn't delete the file after a move up.
When I perform a move task and the a delete task, the server moves and deletes perfectly the file. But I want that both actions can be handled with the move up.
I use the FTP voyager version 16.1.0.0
03] Wed 12Apr17 13:44:16 - Server supports resume.
[05] Wed 12Apr17 13:44:16 - STOR 20170412112901_20170412112858_af_5_4.pdf
[06] Wed 12Apr17 13:44:16 - 200 Don't care
[05] Wed 12Apr17 13:44:16 - OPTS UTF8 ON
[06] Wed 12Apr17 13:44:16 - 150 Opening data channel for file upload to server of "/Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste/20170412112901_20170412112858_af_5_4.pdf"
[06] Wed 12Apr17 13:44:17 - 202 UTF8 mode is always enabled. No need to send this command.
[05] Wed 12Apr17 13:44:17 - PWD
[06] Wed 12Apr17 13:44:17 - 257 "/" is current directory.
[03] Wed 12Apr17 13:44:17 - Opening passive mode data connection to 136.144.129.18, port 49992.
[05] Wed 12Apr17 13:44:17 - STOR 20170412113759_20170412113758_ENI_0.pdf
[06] Wed 12Apr17 13:44:17 - 150 Opening data channel for file upload to server of "/Test/BE0659837055_AF_Aankoopfacturen_BrasserieJuste/20170412113759_20170412113758_ENI_0.pdf"
Seems I can replicate this behavior every time by simply clicking the title bar while any transfer is in progress. It also happens when trying to view a downloaded file from the local browser. I'm using passive mode. The most common fault is:
Faulting application ftp voyager.exe, version 16.0.2.0, faulting module shlwapi.dll, version 6.0.2900.5912, fault address 0x00008440, but also happens on ntdll.dll, ftpvoyage.exe and "Unknown."
If I don't touch it, it seems to work, but almost any interaction with it after or during transfers crashes it.
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.
The SSH_FILEXFER_ATTR_EXTENDED flag provides a general extension
mechanism for vendor-specific extensions. If the flag is specified,
then the ‘extended_count’ field is present. It specifies the number
of extended_type-extended_data pairs that follow. Each of these
pairs specifies an extended attribute. For each of the attributes,
the extended_type field should be a string of the format
"name@domain", where "domain" is a valid, registered domain name and
"name" identifies the method. The IETF may later standardize certain
names that deviate from this format (e.g., that do not contain the
"@" sign). The interpretation of ‘extended_data’ depends on the
type. Implementations SHOULD ignore extended data fields that they
do not understand.
FTP Voyager is incorrectly interpreting these extended attributes as either files or folders, it then reports an error on the parsing of the SSH_FXP_NAME packet, and is unable to list all the files. For example, with all logging enabled including Raw Listings. A listing of a directory that has four files in it, each with seven extended file attributes, results in just the first file displayed with one of the extended attributes displayed as a folder and then an error that it is unable to parse the listing:
With FTP Voyager I can download 3 MB at a time but then the transfer will just hang and we have a 600 MB file to download.
Here is the message: SSH_FXP_STATUS: status: SSH_FX_NO_CONNECTION; description: [2016/11/04 11:54:40.156] SSE2636 Command rejected due to sftp proxy policy settings: SSH_FXP_READ
I also know that the server is running SSH_FXP_VERSION: 3 and FTP Voyager is running as version 6 but I cannot find a place to change this.
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.
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.
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?
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.
