Running an enterprise license - everything has been working fine on multiple machines - just setup a new 64 bit Windows 7 machine. Installed and started up filemaker, opened remote file - first error was that java was not installed and FTPeek needed it - no surpise as (again) new machine.

Closed filemaker - downloaded most recent java version (version 7 update 5) - downloaded (automatically) as 32 bit as IE is a 32 bit version.

Started up again - filemaker starts fine - no error - checked and plugin automatically downloaded from the server (v1.561). went to test to upload file from container - everything fine through selecting the file - when it should upload the file after selecting it it then fails with "connection reset" immediately rather a normal upload bar.

Went to 360 works site - saw a new version is available. downloaded - put on server - restarted filemaker, plugin updated to v1.61.

Tried again - again failed with "connection reset" as before.

Popped the file over to a 64 bit Vista machine - Java version 6 update 26, filemaker starts, updates plugin, went to upload the file - no problem. Note that all of the ftp directory paths and login and password info is tagged into the filemaker file itself. So these clearly work (and have been consistently working for other users).

I am a bit baffled - am leaning toward it being something to do with the Java version - but can't quite understand why. Log of failure and success on the other machine is below. Help!

--------------------------------------------

FAIL:

--------------------------------------------

Jun 19, 2012 2:27:21 PM com.prosc.fmkit.Plugin setLastError

SEVERE: PluginFunction PluginFunction{name='FTPeek_UploadFileFromContainer', functionID=-11068, minArgs=null, maxArgs=2} got an error with converted args [PATH AND FILE, com.prosc.fmkit.types.FMData@1b51db7]

com.enterprisedt.net.ftp.ControlChannelIOException: Connection reset

at com.enterprisedt.net.ftp.FTPControlSocket.A(Unknown Source)

at com.enterprisedt.net.ftp.FTPControlSocket.E(Unknown Source)

at com.enterprisedt.net.ftp.FTPControlSocket.sendCommand(Unknown Source)

at com.enterprisedt.net.ftp.FTPControlSocket.createDataSocketPASV(Unknown Source)

at com.enterprisedt.net.ftp.pro.ProFTPControlSocket.createDataSocketPASV(Unknown Source)

at com.enterprisedt.net.ftp.FTPControlSocket.A(Unknown Source)

at com.enterprisedt.net.ftp.FTPClient.setupDataSocket(Unknown Source)

at com.enterprisedt.net.ftp.FTPClient.initPut(Unknown Source)

at com.enterprisedt.net.ftp.FTPClient.A(Unknown Source)

at com.enterprisedt.net.ftp.FTPClient.B(Unknown Source)

at com.enterprisedt.net.ftp.FTPClient.put(Unknown Source)

at com.enterprisedt.net.ftp.FTPClient.put(Unknown Source)

at com.prosc.ftpeek.GenericFTPModel$4.run(GenericFTPModel.java:709)

Jun 19, 2012 2:27:21 PM com.prosc.fmkit.PluginBridge$3 run

<<BEGINS LAST ERROR>>

--------------------------------------------

SUCCESS:

--------------------------------------------

Jun 19, 2012 3:06:45 PM com.prosc.ftpeek.GenericFTPModel uploadFile

INFO: Uploaded file to remote path PATH AND FILE

Jun 19, 2012 3:06:45 PM com.prosc.fmkit.PluginBridge$3 run

<<BEGINS DISCONNECT>>

Our plugins have not yet been tested with Java 7. That said, it is possible this is the issue. The easy way to test this of course is to remove the 32 bit version of Java 7 and install a 32-bit version of Java 6 (or 5).

Thanks - yes, that did the trick. Until FTPeek is tested to work with version 7 I would suggest updating some of the documentation (since now it's been tested with version 7 and - at least how we are using it - it doesn't work). As an example the user documentation points a link to the java download page - where you get version 7 and just version 7....so you are almost pointing someone to failure if - for whatever reason - java is not already installed! Also, as new machines come online with version 7, or Java updates, this may become more of an issue...So make a clear note - 6 works, use 7 at your own risk. The straight from oracle runtime download of the latest version (pre 7) is here - version 6 update 33:

http://www.oracle.com/technetwork/java/javase/downloads/jre6-downloads-1637595.html

Thanks again!

I understand your point. We are currently in the process of making the plugin compatible with Java 7. As a result, the documentation will likely not change as those changes only "go live" every time we deploy a new version of one of our plugins. In this case, the compatibility with Java 7 should happen sooner and make the documentation change a moot point. The feedback here has been very helpful as we work toward compatibility.

Hi All

This appears to be a bug in Windows firewall as documented in this bug report: http://bugs.sun.com/...?bug_id=7077696

There is a work around that involves setting a JVM flag

-Djava.net.preferIPv4Stack=true

Our plugins currently do not have a way to accept JVM launch args., and even if they did it would be on per machine basis. I'm going to investigate this bug further to see if it makes sense for us to use this flag for Windows plugins.