I'm using ftp Voyager at a daily basis to check remote sites and move down all files.
The task works almost every day. Exception are when the remote ftp site is empty. Here the task will run continuously.
I've tried to turn off keep alive, but it continues to run forever.
I'd like the task to fail, if no files.
Anyone knows what i'm doing wrong?
Thanks.
Just recently our server that is running FTP Voyager, started experiencing some odd things with the scheduler. The tray icon will show up and seem like it is running. Btw, we're running 16.2.0.328. However, when I click on the system tray and try to start the management console, it never comes up. I can kill the processes and try again, but it doesn't change anything. I can see the tray and scheduler processes running in the task manager. Is there any other way to get the management console for the scheduler to come up? Any help would be greatly appreciated.
Our server is Windows Server 2012 R2 Standard.
Thanks
Greg
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
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 ??
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.
Continually getting the following message after a connection is created from FTP Voyager:
SSL accept failed on FTP data channel - The connection will be aborted
Using FTP over TLS - explicit
Works from FileZilla for example to the same host with the same credentials.
Hi,
We are using FTP Voyager 16.1.0.0 & sometimes schedule task stuck. There are 5 actions (Local Folders Synchronize) used. Task log are showing below messages.
Kindly suggest what could be the problem & how to resolve it.
[03] Thu 27Nov14 11:08:09 - Transferred 80,058 bytes. 625.45 KB/sec.
[05] Thu 27Nov14 11:08:09 - XCRC "/DATA/Data_11272014_1_00_02_AM.CSV"
[06] Thu 27Nov14 11:08:09 - 500 'XCRC "/Data/Data_11272014_1_00_02_AM.CSV"': command not understood.
[04] Thu 27Nov14 11:08:09 - XCRC command failed. The command may not be supported by this server.
[03] Thu 27Nov14 11:08:09 - XCRC command checking has been disabled for future transfers using this session.
Regards,
Dhiraj
I was getting errors sending email alerts saying that Voyager could not find the email server on port 25. I switched to a new SMTP server. Setup the email option in FTP Voyager to use Port 587 and the new SMTP server settings. Stopped and restarted the Scheduler service. But still getting error that it cannot send on port 25.
Thanks
Bob
Is FTP Voyager (v 16.2.0.328) TLS 1.1 and/or 1.2 compatible?
I'm new to Voyager FTP. How can I edit the permissions in existing jobs
Hello,
I'm having trouble with this configuration. . .
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.
Any one have similar experience?
Thanks.
Doug
I recently downloaded FTP Voyager to help with syncing files and folders on our Egnyte FTP site. After trying to get AllSync to work with much fail I decided to look else where. Enters FTP Voyager. So I have installed and set-up the software. Connects to Egnyte FTP no problem. I get all the files and folders mapped from our server to the FTP folder and click sync. PERFECT. Voyager takes some time but end result is what has changed and what has been added and or deleted. When I go to sync up the folders the connection times out. I get an error in the log which states unable to change folders. When I try to only sync folders or sometimes multiple files the program hangs. I know the program is free but it is what I am looking for. Any help would be great at solving this problem.
Thanks.
Paul
I am getting this error and I don't know what the problem is.
SSH Disconnect Error: no more authentication methods available.
We are using Serv-U on the back-end and FTP Voyager on the front end.
Regular password based connections work fine.
As soon as I create a private / public key and bind it to the user (on both sides), then the authentication will not work.
Here is the log.
Perhaps I have to disable password authentication before public key authenication will work?
STATUS> Resolving host "abc.myspecialsite.com"...
STATUS> Connecting to "65.212.176.194" on port 22.
STATUS> Connected to 65.212.176.194:22 from 10.0.0.25:58052.
STATUS> Negotiating SSH2 session with server...
STATUS> Client Identification: SSH-2.0-FTP Voyager_16.2.0.328
STATUS> Server Identification: SSH-2.0-2.0
STATUS> Initializing key exchange process...
STATUS> Selected key exchange algorithm: diffie-hellman-group1-sha1
STATUS> Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99
STATUS> Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Selected public key protocol: ssh-rsa
STATUS> Key exchange process successfully completed.
COMMAND> SSH_MSG_SERVICE_REQUEST: service: ssh-userauth
SSH_MSG_SERVICE_ACCEPT: service accepted
STATUS> Querying server for supported authentication methods
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none
SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey
STATUS> Supported authentication methods: password, publickey
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey
ERROR> SSH Disconnect Error: no more authentication methods available.
ERROR> Unable to login.
ERROR> Connection attempt failed. Retrying in 3 seconds...
COMMAND> SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.
ERROR> The server has unexpectedly closed the connection.
ERROR> Connection attempt failed. Retrying in 3 seconds...
STATUS> Retrying Connection (attempt 2)...
STATUS> Resolving host "abc.myspecialsite.com"...
STATUS> Connecting to "65.212.176.194" on port 22.
STATUS> Connected to 65.212.176.194:22 from 10.0.0.25:58054.
STATUS> Negotiating SSH2 session with server...
STATUS> Client Identification: SSH-2.0-FTP Voyager_16.2.0.328
STATUS> Server Identification: SSH-2.0-2.0
STATUS> Initializing key exchange process...
STATUS> Selected key exchange algorithm: diffie-hellman-group1-sha1
STATUS> Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99
STATUS> Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Selected public key protocol: ssh-rsa
STATUS> Key exchange process successfully completed.
COMMAND> SSH_MSG_SERVICE_REQUEST: service: ssh-userauth
SSH_MSG_SERVICE_ACCEPT: service accepted
STATUS> Querying server for supported authentication methods
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none
SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey
STATUS> Supported authentication methods: password, publickey
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey
ERROR> SSH Disconnect Error: no more authentication methods available.
ERROR> Unable to login.
ERROR> Connection attempt failed. Retrying in 3 seconds...
COMMAND> SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.
ERROR> The server has unexpectedly closed the connection.
ERROR> Connection attempt failed. Retrying in 3 seconds...
STATUS> Retrying Connection (attempt 3)...
STATUS> Resolving host "abc.myspecialsite.com"...
STATUS> Connecting to "65.212.176.194" on port 22.
STATUS> Connected to 65.212.176.194:22 from 10.0.0.25:58056.
STATUS> Negotiating SSH2 session with server...
STATUS> Client Identification: SSH-2.0-FTP Voyager_16.2.0.328
STATUS> Server Identification: SSH-2.0-2.0
STATUS> Initializing key exchange process...
STATUS> Selected key exchange algorithm: diffie-hellman-group1-sha1
STATUS> Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99
STATUS> Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Selected public key protocol: ssh-rsa
STATUS> Key exchange process successfully completed.
COMMAND> SSH_MSG_SERVICE_REQUEST: service: ssh-userauth
SSH_MSG_SERVICE_ACCEPT: service accepted
STATUS> Querying server for supported authentication methods
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none
SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey
STATUS> Supported authentication methods: password, publickey
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey
ERROR> SSH Disconnect Error: no more authentication methods available.
ERROR> Unable to login.
ERROR> Connection attempt failed. Retrying in 3 seconds...
COMMAND> SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.
ERROR> The server has unexpectedly closed the connection.
ERROR> Connection attempt failed. Retrying in 3 seconds...
STATUS> Retrying Connection (attempt 4)...
STATUS> Resolving host "abc.myspecialsite.com"...
STATUS> Connecting to "65.212.176.194" on port 22.
STATUS> Connected to 65.212.176.194:22 from 10.0.0.25:58058.
STATUS> Negotiating SSH2 session with server...
STATUS> Client Identification: SSH-2.0-FTP Voyager_16.2.0.328
STATUS> Server Identification: SSH-2.0-2.0
STATUS> Initializing key exchange process...
STATUS> Selected key exchange algorithm: diffie-hellman-group1-sha1
STATUS> Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99
STATUS> Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Selected public key protocol: ssh-rsa
STATUS> Key exchange process successfully completed.
COMMAND> SSH_MSG_SERVICE_REQUEST: service: ssh-userauth
SSH_MSG_SERVICE_ACCEPT: service accepted
STATUS> Querying server for supported authentication methods
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none
SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey
STATUS> Supported authentication methods: password, publickey
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey
ERROR> SSH Disconnect Error: no more authentication methods available.
ERROR> Unable to login.
ERROR> Connection attempt failed. Retrying in 3 seconds...
COMMAND> SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.
ERROR> The server has unexpectedly closed the connection.
ERROR> Connection attempt failed. Retrying in 3 seconds...
STATUS> Retrying Connection (attempt 5)...
STATUS> Resolving host "abc.myspecialsite.com"...
STATUS> Connecting to "65.212.176.194" on port 22.
STATUS> Connected to 65.212.176.194:22 from 10.0.0.25:58060.
STATUS> Negotiating SSH2 session with server...
STATUS> Client Identification: SSH-2.0-FTP Voyager_16.2.0.328
STATUS> Server Identification: SSH-2.0-2.0
STATUS> Initializing key exchange process...
STATUS> Selected key exchange algorithm: diffie-hellman-group1-sha1
STATUS> Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99
STATUS> Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Selected public key protocol: ssh-rsa
STATUS> Key exchange process successfully completed.
COMMAND> SSH_MSG_SERVICE_REQUEST: service: ssh-userauth
SSH_MSG_SERVICE_ACCEPT: service accepted
STATUS> Querying server for supported authentication methods
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none
SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey
STATUS> Supported authentication methods: password, publickey
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey
ERROR> SSH Disconnect Error: no more authentication methods available.
ERROR> Unable to login.
ERROR> Connection attempt failed. Retrying in 3 seconds...
COMMAND> SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.
ERROR> The server has unexpectedly closed the connection.
ERROR> Connection attempt failed. Retrying in 3 seconds...
STATUS> Retrying Connection (attempt 6)...
STATUS> Resolving host "abc.myspecialsite.com"...
STATUS> Connecting to "65.212.176.194" on port 22.
STATUS> Connected to 65.212.176.194:22 from 10.0.0.25:58061.
STATUS> Negotiating SSH2 session with server...
STATUS> Client Identification: SSH-2.0-FTP Voyager_16.2.0.328
STATUS> Server Identification: SSH-2.0-2.0
STATUS> Initializing key exchange process...
STATUS> Selected key exchange algorithm: diffie-hellman-group1-sha1
STATUS> Host Key Fingerprint: E4:DD:11:2E:82:34:AB:62:59:1C:C8:62:1D:4B:48:99
STATUS> Server --> Client: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Client --> Server: Encryption: aes128-cbc, MAC: hmac-sha1, Compression: zlib
STATUS> Selected public key protocol: ssh-rsa
STATUS> Key exchange process successfully completed.
COMMAND> SSH_MSG_SERVICE_REQUEST: service: ssh-userauth
SSH_MSG_SERVICE_ACCEPT: service accepted
STATUS> Querying server for supported authentication methods
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: none
SSH_MSG_USERAUTH_FAILURE: partial: 0; available authentications: password, publickey
STATUS> Supported authentication methods: password, publickey
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_PK_OK: public key algorithm accepted
COMMAND> SSH_MSG_USERAUTH_REQUEST: user: abc.myspecialsite.com|bear-user; service: ssh-connection; type: publickey
SSH_MSG_USERAUTH_FAILURE: partial: 1; available authentications: password, publickey
ERROR> SSH Disconnect Error: no more authentication methods available.
ERROR> Unable to login.
ERROR> Connection attempt failed. Retrying in 3 seconds...
COMMAND> SSH_MSG_DISCONNECT: reason code 14; description: SSH Disconnect Error: no more authentication methods available.
ERROR> The server has unexpectedly closed the connection.
ERROR> Connection attempt failed. Retrying in 3 seconds...
STATUS> Retrying Connection (attempt 7)...
STATUS> Resolving host "abc.myspecialsite.com"...
STATUS> Connecting to "65.212.176.194" on port 22.
STATUS> Connected to 65.212.176.194:22 from 10.0.0.25:58064.
STATUS> Negotiating SSH2 session with server...
STATUS> Client Identification: SSH-2.0-FTP Voyager_16.2.0.328
ERROR> The server has unexpectedly closed the connection.
ERROR> Could not establish a connection to MFT-AIM.
Hi folks,
I'm attempting to synchronize with a remote FTP site against my network directory. The remote FTP directory automatically renames the file upon download. When I setup a schedule and executed it manually, I'm getting a "Download of "\\<local network share which I'm synchronizing with>" failed message. Why is it attempting to download from my network share?
Below is the log from FTP Voyager. My question is, why is it attempting to "download" from my local directory?
[05] Tue 10Feb15 11:36:32 - RETR <remote ftp folder>/QSBCUST.001 [06] Tue 10Feb15 11:36:32 - 150 Opening data connection for <remote ftp folder>/QSBCUST.001. [06] Tue 10Feb15 11:36:33 - 450 File unavailable. [04] Tue 10Feb15 11:36:33 - Download of "\\<local network location>\QSBCUST.001" failed. [04] Tue 10Feb15 11:36:33 - Retrying failed transfer (attempt 2 out of 3)... [03] Tue 10Feb15 11:36:33 - SSL connection established. All transactions are now secure. [03] Tue 10Feb15 11:36:33 - Encryption cipher: 128 bit RC4; Version: TLSv1/SSLv3. [03] Tue 10Feb15 11:36:33 - Receiving: <remote ftp folder>/QSBCUST.001 -> \\<local network location>\QSBCUST.001 [05] Tue 10Feb15 11:36:33 - PASV
The synchronization seems to happen successfully, all new files are downloaded from the remote FTP to my local network directory, although the automatic rename on the remote server is no longer happening. I'm thinking this is no coincidence?
Any help would be greatly appreciated.
Thanks,
Michael Murray
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.
"
"
Hi,
We have a scheduled task that should upload a file to a remote location via FTP over SSL or TLS. This was working fine with version 15 but not now with version 16. The upload works sometimes but most of the time it doesn't.
We really need this to work or else a downgrade must be done. So any ideas or questions will be appreciated.
Kind regards,
Peter Nilsson
STATUS> Resolving host "ftps.xxxxx.xx"...
STATUS> Connecting to "nnn.nnn.nnn.nnn" on port 21.
STATUS> Connected to nnn.nnn.nnn.nnn:21 from nnn.nn.n.nnn:64626.
220-FTP 10:12:22 on 2016-03-15.
220 Connection will close if idle for more than 5 minutes.
COMMAND> AUTH TLS
234 Security environment established - ready for negotiation
STATUS> SSL connection established. All transactions are now secure.
STATUS> Encryption cipher: 256 bit AES; Version: TLSv1/SSLv3.
STATUS> Connected. Logging in to the server.
COMMAND> USER xyz
331 Send password please.
COMMAND> PASS ***
230 xyz is logged on. Working directory is "/remotefolder1/remotefolder2/out".
STATUS> Login successful.
COMMAND> SYST
215 UNIX is the operating system of this server. FTP Server is running on z/OS.
COMMAND> FEAT
211- Extensions supported
SIZE
MDTM
AUTH TLS
PBSZ
PROT
211 End
COMMAND> REST 100
504 Restart requires Block or Compressed transfer mode.
STATUS> Server supports resume.
COMMAND> PBSZ 0
200 Protection buffer size accepted
COMMAND> PROT P
200 Data connection protection set to private
COMMAND> PWD
257 "/remotefolder1/remotefolder2/out" is the HFS working directory.
COMMAND> CWD /remotefolder1/remotefolder2/in
250 HFS directory /remotefolder1/remotefolder2/in is the current working directory
COMMAND> PASV
227 Entering Passive Mode (nnn,nnn,nnn,nnn,nnn,nn)
STATUS> Opening passive mode data connection to nnn.nnn.nnn.nnn, port 60734.
STATUS> Negotiating SSL connection with server...
COMMAND> LIST /remotefolder1/remotefolder2/in/File123.txt
550 LIST cmd failed : ls: FSUM6785 File or directory "/remotefolder1/remotefolder2/in/File123.txt" is not found
STATUS> Sending: \\localserver\localfolder1\localfolder2\out\File123.txt -> /remotefolder1/remotefolder2/in/File123.txt
COMMAND> TYPE A
ERROR> SSL Accept failed on FTP data channel. The connection will be aborted.
STATUS> Resolving host "ftps.xxxxx.xx"...
STATUS> Connecting to "nnn.nnn.nnn.nnn" on port 21.
STATUS> Connected to nnn.nnn.nnn.nnn:21 from nnn.nn.n.nnn:64630.
220-FTP 10:12:25 on 2016-03-15.
220 Connection will close if idle for more than 5 minutes.
COMMAND> AUTH TLS
234 Security environment established - ready for negotiation
STATUS> SSL connection established. All transactions are now secure.
STATUS> Encryption cipher: 256 bit AES; Version: TLSv1/SSLv3.
STATUS> Connected. Logging in to the server.
COMMAND> USER xyz
331 Send password please.
COMMAND> PASS ***
230 xyz is logged on. Working directory is "/remotefolder1/remotefolder2/out".
STATUS> Login successful.
COMMAND> SYST
215 UNIX is the operating system of this server. FTP Server is running on z/OS.
COMMAND> FEAT
211- Extensions supported
SIZE
MDTM
AUTH TLS
PBSZ
PROT
211 End
COMMAND> REST 100
504 Restart requires Block or Compressed transfer mode.
STATUS> Server supports resume.
COMMAND> PBSZ 0
200 Protection buffer size accepted
COMMAND> PROT P
200 Data connection protection set to private
COMMAND> PWD
257 "/remotefolder1/remotefolder2/out" is the HFS working directory.
COMMAND> QUIT
221 Quit command received. Goodbye.
I Use FTP Voyager Scheduler for auto upload/download file to FTP server
I have around 10 FTP task with scheduler , 1 day all task scheduler stop running and when I go to log file , I see that 1 task keep running forever so causes the other sessions all are in queue.
My question is do you have any mechanism /solution so that can try to stop a session if it run for example more than 5 minutes.
Or we have any monitor so we know which task schedule frozen , tks
Do FTP voyager keep a history for the status log?
Hello,
when i try connect to ftp i get error:
SSL accept failed on FTP data channel.
The connection will be aborted
but i can connect with FileZilla or other ftp clients.
FTP Voyager 16.2.0.328
log:
STATUS> Resolving host "ftp.xxxxxx.xx"...
STATUS> Connecting to "xxx.xxx.xxx.xxx" on port 990.
STATUS> Connected to xxx.xxx.xxx.xxx:990 from 10.10.10.10:56773.
STATUS> Negotiating SSL connection with server...
STATUS> SSL connection established. All transactions are now secure.
STATUS> Encryption cipher: 256 bit AES; Version: TLSv1/SSLv3.
220 (vsFTPd 3.0.2)
COMMAND> HOST ftp.xxxxxx.xx
530 Please login with USER and PASS.
STATUS> Connected. Logging in to the server.
COMMAND> USER ftp-baku
331 Please specify the password.
COMMAND> PASS ***
230 Login successful.
STATUS> Login successful.
COMMAND> SYST
215 UNIX Type: L8
COMMAND> FEAT
211-Features:
AUTH TLS
EPRT
EPSV
MDTM
PASV
PBSZ
PROT
REST STREAM
SIZE
TVFS
UTF8
211 End
STATUS> Server supports resume.
COMMAND> OPTS UTF8 ON
200 Always in UTF8 mode.
COMMAND> PBSZ 0
550 Permission denied.
COMMAND> PROT P
550 Permission denied.
COMMAND> PROT C
550 Permission denied.
COMMAND> PWD
257 "/"
COMMAND> PASV
227 Entering Passive Mode (82,138,52,71,34,222).
STATUS> Opening passive mode data connection to xxx.xxx.xxx.xxx, port 8926.
STATUS> Negotiating SSL connection with server...
COMMAND> LIST
150 Here comes the directory listing.
226 Directory send OK.
ERROR> SSL Accept failed on FTP data channel. The connection will be aborted.
Please help me with solving a problem.
I have setup FTP Voyager to upload and download files from serval sources successfully but wish to email particular business owners a list of the files uploaded or downloaded via the event management send an email notification
Is this possible
An alternative may be to email the log file generated once the job has completed successfully is this possible?
Kind Regards
Keith Taylor