Jump to content

FTPeek Auto-Update Issue on Windows

This topic is 2055 days old. Please don't post here. Open a new topic instead.

Recommended Posts

I have a client using Windows 8 that is getting an error when trying to auto-update the new version of FTPeek. We're using the 360Works hosted update database. It worked fine on a Mac at the client location using the same database. The error is "FTPeek failed to initialize". When I looked in the extensions folder, the new plug-in was there with a .new extension and the old one was intact. Any ideas what would cause this?

Link to post
Share on other sites

The versions of our plugins that we released last week, including FTPeek version 1.66, can't be auto updated over the old versions, due to auto update having issues in those old versions. If you manually remove all copies of our plugins (possibly aided by our auto-updated plugin removal tool at http://static.360works.com/remove-plugins ), you should then be able to install the new version (automatically or manually).


If you're still having any issues, check to see if any logs are being generated in your C:Users[username]360Works directory and attach them if so.

Link to post
Share on other sites

Auto-update isn't supported or expected to work on any platform when updating from the old versions to any of the new versions released last week. It's definitely possible that it could work in certain situations, as you've seen. 

Link to post
Share on other sites

This topic is 2055 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Similar Content

    • By lepak
      When I try to activate 360Works_FTPeek (v1.67) on my freshly installed OS X Yosemite with FileMaker Server 14, nothing happen in the web UI (except that the logs say that FileMaker ScriptEngine crashed suddenly)
      I then took a look at FM logs, and found this (files cleaned just before enabling the plugin) : 
      Unable to find any JVMs matching architecture "i386".
      No Java runtime present, requesting install.
      2015-08-14 15:41:14.499 fmsased[296:1827] JLRequestRuntimeInstall: Error calling: CFMessagePortCreateRemote
      (C++ Fri Aug 14 15:41:14 2015) Unrecognized manifest key: Permissions
      (C++ Fri Aug 14 15:41:14 2015) Unrecognized manifest key: Codebase
      (C++ Fri Aug 14 15:41:14 2015) Finished reading metadata; (360Works FTPeek) (F3TP1YnYnnn) (File Transfer Protocol (FTP) plugin. Also supports secure connections with SFTP and FTPS.) (1.67)
      (C++ Fri Aug 14 15:41:14 2015) INIT - Creating new log file
      (C++ Fri Aug 14 15:41:14 2015)  *** INIT for 360Works FTPeek_ServerScripting64 at Fri Aug 14 15:41:14 2015, headless mode 1, appTypeShort 7, JaCK version 2.0
      (C++ Fri Aug 14 15:41:14 2015) Detected 64-bit environment. Will look for 64-bit JDK home.
      (C++ Fri Aug 14 15:41:14 2015) Java home dir was dynamically read: /Library/Java/JavaVirtualMachines/jdk1.8.0_51.jdk/Contents/Home
      (C++ Fri Aug 14 15:41:14 2015) Opening dylib at /System/Library/Frameworks/JavaVM.framework/JavaVM
      I have Java SDK 1.8.0u51 installed in the standard location (as seen in logs). And at FileMaker Server installation, as there was not yet any JDK, I let it installed JRE 1.8.0u51 so I have both.
      Any hint on what's happening here? Should I install an older JDK for this plugin?
    • By laurentades
      Weird issue here.
      Running FMS 13.0v5 and FTPeek 1.66 enterprise on OS X 10.10.
      I am working on a script A calling FTPeek upload to FTP. Script B calls script A as part of an overall process.
      When i call script B from script A with usual Perform Script, everything works fine.
      However when i call it with Perform Script on Server (PSoS) - which is supposed to be supported by enterprise license - the script basically hangs. Then the FMS Admin-Console Activity/Clients shows a client connection as "FileMaker Script" which will basically won't leave the queue - even if I send a disconnect message. Only way to solve the issue is restart the entire host...!  When running in debug mode from FMP, the moment script B calls script a with PSoS, FMP just freezes and I need to force quit it.
      I understand that 1.66 brought support for PSoS but that only applies to enterprise license which is what i have as my order confirmation message tells me so...
      Any idea anyone ?
      Logs attached.
    • By tvGuy
      I just upgraded from FMS12 to 14 and I'm having trouble getting the FTPeek plugin to install.    During the FMS upgrade I upgraded to Yosemite.     
      Here's what I'm seeing:
      Go to Admin Console UI Select Database Server Select Server Plug-ins See 360Works_FTPeek.fmplugin in bottom window & the plugin is "not loaded" Click "Enable FileMaker Script Engine (FMSE) to use plug-ins" Click the checkbox for the row of the FTPeek plugin. Check box gets clicked. Toast message appears that says FTPeek plugin has been enabled the Check box immediately gets unchecked Error is logged:  Plug-in failed to load: 360Works_FTPeek.fmplugin  I found the thread below and followed the directions installing the Mac Java version but still no luck.   Any ideas.

    • By tvGuy
      I just upgraded Server & Clients to FMP14, but when I try to activate the FTPeek plugin on my client I receive the following error:
      I'm using Mac if that matters.
      Any idea what this means?   
    • By mtolman
      Having trouble registering FTPeek on a new windows server that we are upgrading to.  Interestingly, it was working fine on our old FileMaker 12 server, but can't get it to register on the new FileMaker 13 server. 
      If I use a filemaker client and run the script it registers fine and reports back:
      360Works FTPeek v1.642
      Major Version: 1
      Type: Enterprise License
      On the server it loads and enables the plugin, but when I try to run that same script it hangs on the register script step (I played around with where I put an exit script step and am sure it is on that one script step).  It never finishes that script step and the routine just sits there and runs forever.   Have tried rebooting the server, and restarting the script engine.  Also played around with different Java versions, and can't seem to get it working. 
      Current configuration is: 
      FTPeek 1.642
      FileMaker Server 13.03
      Window 2008 Server
      Java update 51 (64 bit)
      Java update 67 (32 bit)  - note I also tried the 32 bit version of Java Update 51 which had the same behavior before I upgraded to the latest version to see if that would work.
      Any ideas of what else I can try?  I am sure I have the plugin installed and running in the right spot and I can see in the logs that the plugin is enabled on the server. 

  • Create New...

Important Information

By using this site, you agree to our Terms of Use.