We have corrected a number of issues in 220.127.116.11, the current release. I strongly recommend updating to the latest release, which you can download from www.FTPVoyager.com/download. Once you have updated, if the issue persists, I have a few questions:
1) What protocol are you connecting with? FTP, FTPS, or SFTP?
2) What is the average size of CSV file you are downloading?
3) Which file server is running on the remote side, and on which platform?
4) Can you provide a log of your connection by logging on, attempting the download, and copying the log from the "Log Pane" to a file and attaching it to your reply?
Look forward to your reply!
I am experiencing the exact same issue. I have additional diagnostic information.
- Version 18.104.22.168, downloaded 2 days ago
- If I sync from the Voyager UI, it works. If I sync from Scheduled Sync, it fails with the same symptoms (0kb files)
I have enabled logging, and here is what I found
- Scheduled Sync submits a RETR command, which is failing with code "550: no such file or directory"
- Scheduled Sync and the Voyager UI each submit a slightly different RETR command
- Voyager UI: RETR /Outbound/myd121222_0720.txt (note the "/" in front of the folder name)
- Scheduled Sync: RETR Outbound/myd121222_0720.txt (note that there is no "/" in front of the path)
I have log files available, but will not submit them to a public forum.
I was referred to this forum by Rhinosoft, with whom I have a Serv-U Gold license. I am evaluating FTP Voyager to add to our tool chest.
I am really nervous that the only support for FTP Voyager is via a public forum, and there doesn't appear to be any official support channel other than this. If we integrate FTP Voyager scheduled sync into our mission critical operations, I need to know that there is a phone number I can call if there is a problem and get a quick resolution. The lack of such support may well be a dealbreaker. I don't mind paying for maintenance, but I need something better than this.
1 of 1 people found this helpful
What is the remote path set to in your Synchronize task? Scheduler requires full paths to be used. For example:
Good Remote Paths
Remote File or Folder: /
Remote File or Folder: /ciscocm/recordings
Bad Remote Paths
Remote File or Folder: (nothing, empty)
Remote File or Folder: ciscocm/recordings
The path must begin with a "/" and must be absolute paths, not relative paths. Using a relative path or not starting the path with a "/" could produce the RETR result you see.
Thomas, thank you... that corrected the issue. As you suspected, there was no “/” in the remote path.
You guys may still have a bug in the software, as the remote path was created by the wizard.
If you could indulge me, I have several more questions before I can complete my evaluation:
- Can you please advise what our support options are if the software fails on one of our mission-critical jobs? Are there different support levels or maintenance contracts?
- We want to prevent our automated systems from acting on corrupted or partially downloaded files. Our automated systems scan the local folder looking for file names. What do you recommend?
- Is it possible for Voyager to use a temporary file name until the transfer is complete?
- Is it possible for Voyager to delete the file if the transfer is interrupted?
At this time, FTP Voyager support is only available via Thwack - we are not currently offering support contracts or other maintenance levels. It also currently does not support the use of temporary file names or locking of the file during download, or deletion of the file in case of a corrupt/interrupted download.
Ouch... You guys have a very nice product, but I am not sure about these downsides.
Thanks for the information.
Dan needs to mark this question Answered, as your answer did resolve the issue.
Cheers Thomas, I put the / in on the Remote Path and it worked a treat.