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 ?
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 Jason Mundok
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?
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:
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.