Hallo CM,

das geht – allerdings mit unserem Produkt WatchDirectory und dem dortigen Plugin „autom. Dateien auf einen FTP-Server hochladen“:
https://de.watchdirectory.net/wdhelp/plugins/wdopAutoFtp_deu.html

Beachte bitte, dass WatchDirectory nicht mit Passwortdateien für FTP verwendet werden kann.
Gerne unsere Demo testen: https://de.watchdirectory.net/download.html

Wir benutzen WatchFTP seit geraumer Zeit erfolgreich zur Überwachung von FTPs externer Partner, würden nun aber gern lokal aktualisierte Dateien auf unseren FTP synchronisieren und die vorhandenen Dateien gleichen Namens entsprechend überschreiben.
Geht das?

Hi,

This is most likely fixed in this beta (64bit version):
http://www.watchftp.com/downloads/SetupWatchFTP_422_x64_beta2.exe
or the 32bit version:
http://www.watchftp.com/downloads/SetupWatchFTP_422_beta2.exe

We are currently working on a new release that implements the latest (1.3) TLS security. It should be ready somewhere next month.

I have a licensed version of WatchFTP 4.2.1 and recently started having issues with the Secure FTP with TLS  over port 21. The initial connection works but then it tries to change to SSL\TLS and fails. The site admin suggested that security updates to the site may have broken the handshake because WatchFTP is not up to date. Are there any new versions planned with updated security?

Here is the log.

ChilkatLog:
 Connect_Ftp2:
   DllDate: Dec 21 2018
   ChilkatVersion: 9.5.0.76
   UnlockPrefix: WTCHDR.CBX0522
   Architecture: Little Endian; 64-bit
   VerboseLogging: 0
   ProgressMonitoring:
     enabled: yes
     heartbeatMs: 0
     sendBufferSize: 65536
   --ProgressMonitoring
   ImplicitSsl: 0
   AuthTls: 1
   AuthSsl: 0
   ftpConnect:
     Hostname: <FTP SITE>
     Port: 21
     IdleTimeoutMs: 20000
     socketOptions:
       SO_SNDBUF: 262144
       SO_RCVBUF: 4194304
       TCP_NODELAY: 1
       SO_KEEPALIVE: 1
     --socketOptions
     readCommandResponse:
       replyLineQP: 220 FTP server ready.
     --readCommandResponse
     initialStatus: 220
     initialResponse: 220 FTP server ready.
     converting to secure connection...
     authTls:
       simpleCommand:
         sendCommand:
           sendingCommand: AUTH TLS
         --sendCommand
         readCommandResponse:
           replyLineQP: 234 AUTH TLS successful
         --readCommandResponse
       --simpleCommand
       clientHandshake:
         clientHandshake2:
           readHandshakeMessages:
             processAlert:
               TlsAlert:
                 level: fatal
                 descrip: handshake failure
               --TlsAlert
               Closing connection in response to fatal SSL/TLS alert.
             --processAlert
             Aborting handshake because of fatal alert.
           --readHandshakeMessages
         --clientHandshake2
       --clientHandshake
       Client handshake failed. (1)
       connectionClosed: 0
       Failed to convert channel to SSL/TLS
     --authTls
   --ftpConnect
   Failed to connect to FTP server.
   Failed.
 --Connect_Ftp2
--ChilkatLog

Hi, thanks for the quick reply.

I forgot to mention, that I want to rename the file on the FTP server, not locally. And additionally I want to avoid downloading files with the given prefix, just like the in build option for the suffix.

But after thinking this through again, it does not matter. I will simply use your suffix method.

Thanks again.

If you enter
{dir}/prefix_{filename}
as the suffix it should work the way you want and rename the FTP file. What you enter must resolve to a full path on the server and all directories must already exist.

You can use all the {tags} mentioned on this page: https://www.watchftp.com/wfhelp/dynamic_naming_en.html

HI,

at the moment there is only an option to rename the while file with a specific suffix. I.e. a *.pdf becomes a *.pdf_SUFFIX

I think it would be good if there were an option to set a prefix

for example

test.pdf becomes PREFIX_test.pdf

Just an idea.

yours David

That looks like a bug.....
I *think* (not sure) it should be checking the path until the last "\", looks like it checks until the first "{".

I will look into it for the next release. For the moment, it should work if you apply a different dynamic name like
E:\FTPRoot\WatchFTP\MarketForce\Inbound\{filetitle}_rascal.edi
or
E:\FTPRoot\WatchFTP\MarketForce\Inbound\rascal\{filetitle}.edi
(and obviously, create the rascal subdirectory)

When trying to dynamically name a file to
E:\FTPRoot\WatchFTP\MarketForce\Inbound\rascal_{filetitle}.edi
I encounter a message "{Dynamic Name} must start with an existing directory. E:\FTPRoot\WatchFTP\MarketForce\Inbound\rascal_ does not exist.

I'm trying to name the file "rascal_{fileTitle}.edi" as per the screenshot.

BTW the path E:\FTPRoot\WatchFTP\MarketForce\Inbound does exist.

Hi,

WatchFTP asks the FTP Server for a directory listing but receives an error instead. The task will "try again" after a few seconds. Those errors typically resolve themself after a few minutes (most likely, the FTP server is temporarily too busy).
I will contact you on your email in a moment.