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"
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?
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.
Looking on some help with this connection issue. I've tried passive mode, turned most options off and then one at a time...to troubleshoot and still no luck.
Trying to connect to and IBM MVS through FTP Voyager and getting directory listing error.
FTP Voyager - Version 16.2.0.328
[14:15:05] STATUS> Connecting to "*.*.*.*" on port **. [14:15:05] STATUS> Connected to *.*.*.*:* from *.*.*.*:******. [14:15:05] 220-FTPD1 IBM FTP CS V1R13 at ****.********.******.*******, *:*:* on 2016-02-24. [14:15:05] 220 Connection will close if idle for more than 10 minutes. [14:15:05] COMMAND> AUTH SSL [14:15:06] 234 Security environment established - ready for negotiation [14:15:06] STATUS> SSL connection established. All transactions are now secure. [14:15:06] STATUS> Encryption cipher: 256 bit AES; Version: TLSv1/SSLv3. [14:15:06] STATUS> Connected. Logging in to the server. [14:15:06] COMMAND> USER ******** [14:15:06] 331 Send password please. [14:15:06] COMMAND> PASS *** [14:15:06] 230 ****** is logged on. Working directory is "******.". [14:15:06] STATUS> Login successful. [14:15:06] COMMAND> SYST [14:15:06] 215 MVS is the operating system of this server. FTP Server is running on z/OS. [14:15:06] STATUS> Server supports resume. [14:15:06] COMMAND> PBSZ 0 [14:15:06] 200 Protection buffer size accepted [14:15:06] COMMAND> PROT P [14:15:06] 200 Data connection protection set to private [14:15:06] COMMAND> PWD [14:15:06] 257 "******.'" is working directory. [14:15:06] COMMAND> CWD '******.' [14:15:06] 250 "******." is the working directory name prefix. [14:15:06] COMMAND> PORT *,*,*,*,*,* [14:15:06] 200 Port request OK. [14:15:06] COMMAND> LIST [14:15:06] 550 No data sets found. [14:15:06] ERROR> The default directory specified for this site profile is not accessible. Please double-check your site profile settings. Trying to access home directory instead...
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?
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.
I realize that the company has little incentive to worry about how their free FTP client inter-operates with a rival server product, but I wondered if anyone had any clues about my problems connecting to IIS FTP server. (Long ago I purchased Serv-U for my now geriatric server, and once owned an actual purchased copy of FTP voyager back when it was a paid product. But by the time moved to a new server, Serv-U went upscale and is way too expensive for my humble purposes.)
I get two types of error, which might or might not be related:
1) When uploading multiple files at once to the server, the connection always hangs on the second file after successfully uploading one file. IIS log looks like this:
This is just uploading a bunch of random images to a folder called "transfer". After the LIST command for the second filename (to see if it's already there), and another PASV command, everything poops out.
2) I get a lot of "SSL Accept Failed on FTP Data Channel" errors. These pop up any time I try to upload a file when a file of the same name already exists in the destination folder; and also at random other times. To get anything done, I need to delete or rename any file of the same name from the server first before uploading; and when the "SSL Accept ..." error pops up at other random times, I need to refresh the destination folder and try again, sometimes repeating this cycle several times. Eventually it always works, but it's a pain. The IIS log file for an attempt to upload a file which already exists, generating the "SSL Accept ..." error, looks like this:
It's not very informative. It gets as far as verifying that the alternative filename is available, and then poops out. IIS FTP server seems to have no more logging detail available. It's not just a dumb-nuts firewall problem, since I can upload individual files one at a time in passive mode using the tricks mentioned above.
We have a scheduled task on the FTP Voyager Scheduler that is supposed to check a local folder every 2 hours and move all zip files (*.zip) from it to a remote folder if there are any.
The move up task seems to be running normally, uploading the files to the remote folder, but each time the task runs, only the last file is transferred completely and the files before that only partially (9 kB each).
After the upload, none of the files in the local folder are deleted. The log doesn't have any indication of any failures.
Am I doing something wrong or is the FTP Voyager having a problem with the remote server I'm trying to work with?
[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.
I am experiencing the strangest behavior on some scheduled tasks. I have a server that I connect to several times a day to transfer different files to the exact folder destination location. I have several tasks to move certain files at different scheduled times all using the same same site profile connection. for the most part it works fine and then one task will fail until I add the ~ in front of the path on that task. other tasks still work fine without it. the log shows that it is trying to create the same path and fails. so in the remote path I have /folder1/folder2/folder3 and that is the same path for all tasks. on one task I need to add the relative path ~/folder1/folder2/folder3 and then it works.
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 utilizing the FTP Voyager client to down a 10MB file over an SFTP connection. It will download about half of the file and then fail giving an SSH_FXP_STATUS: status: SSH_FX_FAILURE; description: Invalid message length in SFTP protocol [808531500] error message. If I wait for the client to give the Disconnect message and then retry the download using the Resume option it will complete the transfer. I have tried this with the 16.2.0.328 and the 16.0.2.0 clients. Since this is a scheduled task, the resume option is not very practical. Are there any options that I can configure to keep this connection working to complete the full download in one attempt
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.
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"