![]() The only solution I know of is restarting things. Getting the "host's capacity" message is something that has happened to me when installing plugins some times. You'll then want to restart the database server and possibly the script engine. Now scan the listings to make sure everything is fmserver:fmsadminįor any you find which are not set with the fmserver owner and fmsadmin group then you'll needed to change them with chmod (run 'man chmod' for more info) Within the Terminal you would check this by using the following commands (this is for Mac - Windows would be different)Ĭd /Library/FileMaker\ Server/Database\ Server/Extensions You may not be able to update it if it isn't owned by the fmserver:fmsadmin user and group. You mention the plugin was "installed manually" and if it was copied then you need to check the permissions and ownership on it. FileMaker Server is probably very permissions sensitive - as is the case with most daemons. I have come across similar issues and I don't know what the reproducible steps are. ![]() This video provides all the critical know-how in order to start working with PSoS and it will get you going fast! You can update hundreds of thousands of records with lightning speed or generate a hundred page report as a PDF within minutes instead of hours. You can send hundreds of thousands of emails without ever seeing a spinning waiting indicator. With PSoS, you can import hundreds of thousands of records in mere seconds. If your solutions are stuck in versions prior to 13, then you might want to beg, borrow or steal (ok, not steal) to start using this feature. Changing the way you think about FileMaker development, using PSoS for short, is inevitable. Until you start using it, it "seems" like it's just "another feature". This is essentially what this new script step does, but with all the power of what FileMaker can do. Your client, a web browser, makes a request to some beefy server and it wrangles the data and then reports back with the compiled results. This is fundamentally why the web is so popular. ![]() There's so much power in how it can be used, that it truly is a game changer. Yes, I said that with all caps! This is exciting! For more information on the process, open the database at fmnet://AutoUpdate360Works (or at fmnet:/ Script on Server is the one step which will change how you develop FileMaker solutions FOREVER. We also offer an AutoUpdate file to help install or update any of our plug-ins. Our AutoUpdate file (see below) uses this method for FileMaker 12+. This script step will install plug-ins in the location associated with the context the script is run in. You can then call the function Get (InstalledFMPlugins) to see the display name, version, and state. This makes it possible to deploy your solution with a plug-in bundled in that installs and registers itself with a script. Simply insert the plug-in into a container field, and call a script including that script step. In FileMaker 12+, you can install and update plug-ins from container fields using the Install Plug-In File script step. Note that only plug-ins installed in the script engine will show up in the Admin Console plug-ins installed in Web Publishing will not. For FMS Web Publishing Engine, restart the WPE itself, either through the Admin Console or the fmsadmin tool. ![]() For FileMaker Server, restart the FileMaker Script Engine using the fmsadmin tool. For FileMaker Pro, just restart the application. After installing a plug-in in any location, that platform needs to be restarted. To manually install, place the plugin file in the proper location for the context in which you wish to use the plugin. On Windows, you will need a current version of Java, which you can download from Oracle.Īll 360Works plug-ins also, of course, require one of the FileMaker platforms to function. For Mac OS 10.7+, you can find this here, or for Mac OS 10.6, here. On OS X, we require the Apple-provided Java 6. FileMaker Pro will prompt you on startup to download the appropriate software if it is not found on your computer, but FileMaker Server has no such prompt, and you will need to manually download a 64-bit JRE if you do not already have one. 360Works plug-ins require a Java Runtime Environment (JRE) in order to run, where the bitness (32 bit or 64 bit) of the JRE matches the bitness of FileMaker.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |