ScriptMaster Plugin not loading

[daehl]

Help! I'm having a terrible morning. Just tried upgrading my ScriptMaster plugin from 1.66 to 2.0 and it's not working. In fact, I can't get 1.66 to work anymore either.

I am running FMP Adv Server 9.0.3.325 on a iMac G5 running Mac OS 10.4.11 and Java version 1.5.0.13.

The FMP Server and my solution have been running fine for months without any problem, but my attempt to upgrade to ScriptMaster 2.0 has been disatrous so far.

I removed the older ScriptMaster 1.66 plugin, and installed the scriptMaster 2.0 plugin in both the folders:

..FileMaker ServerDatabase ServerExtensions360Works_ScriptMaster.fmplugin

..FileMaker ServerWeb Publishingpublishing-enginewpcPlugins360Works_ScriptMaster.fmplugin

Then I changed permissions on both files using the terminal command:

chmod g+wrx

When I restart my FMP Server and check the Admin Console Database Server Configuration screen, it shows the 360Works ScriptMaster plugin listed, but in the description below, it still reports "Allows execution of interpreted java/groovy code. (1.66)"

I've restarted the server and the computer--numerous times, and even removed the ScriptMaster plugin completely, yet the Admin Console still reports "Allows execution of interpreted java/groovy code. (1.66)" in the plugin description EVEN WHEN NO SCRIPTMASTER PLUGIN IS LOADED OR LISTED ABOVE.

Is there some plist or server preference file I need to purge? I can't figure out what's going wrong. I've tried reverting to the 1.66 plugin and no matter what I do, all I get is an error emailed to me from the server:

FileMaker Server 9.0.3.325 on SXFMP reported the following event:

2008-10-16 10:24:23.935 -0500 Error 474 SXFMP Plug-in failed to load: 360Works_ScriptMaster.fmplugin

How do I get ScriptMaster working again?!?! Preferably version 2.0, but I'd settle for 1.66 at this point.

Heeeellllp!

UPDATE: I just tried re-downloading a fresh copy of ScriptMaster 2 and I see there's a 2.0.3 version released a couple days ago. I'll try using that and hope to almighty it works!

UPDATE: Darn it! Still same situation. I installed the ScriptMaster 2.03 plug in, restarted FMPAS9, but the Admin Console still reports the plugin as 1.66, and it gives an error 474 when trying to load it. How is this possible???

Edited October 16, 2008 by Guest

[daehl]

This is so frustrating. I'm not sure what the problem is. After another attempt at restarting I see the following in the Admin Console. (I only have one plugin in the folder, but it's listing two and the File name is a truncated FMP database name ?!?!

So I don't know if I can even trust what the Admin Console is displaying. And below that is where I see the Scriptmaster plugin description. No matter whether it's installed or not.

I'm guessing there's got to be a config file or plist I can trash to help this situation, but I just am not finding any info that is helping the situation...

[daehl]

} Finally got it working...

The Admin Console does seem to have some bugs in how it displays plugin info. Even when no plugins were in either folder, it still reported strange info in the Console (like above).

But the real solution here was to set the plugin's permission group to fmsadmin. I forgot about that originally, but I continued having problems implementing that change after I re-familiarized myself with that requirement. For some reason, when I tried to change it in the Finder, it would let me authenticate as admin and make he change, but when I closed the get info window it would revert back to the original setting. I tried using chown as well, but to no avail. Eventually I set the permissions on the parent folder and had it apply to all enclosing items and that did the trick.

[shmert]

Thanks for posting your fix, D!

[daehl]

One thing that caused a lot of the confusion (and frustration) was that I expected the upgrade to be quickly reversable if it failed, but it was not. Mainly because I didn't consider the plugin's group ownership, but also because I didn't expect them to change. But they did, and that's why I couldn't get ScriptMaster 1.66 working again.

You see, I dragged the 1.66 plugins out of the appropriate FMP Database & Web Server folders before I installed version 2.0, and when the upgrade didn't work, I fully expected to just be able to reverse the process just by turning off the database server, swapping plugins to their original places, and restarting the server. But that didn't work!

Apparently, when the plugins were moved to new folders, their group ownership automatically changed, so when I put them back, they wouldn't load anymore... maybe that's common knowledge to unix experts, but that sure took me by surprise when I finally noticed it!

Just an FYI in case anyone else every runs into the same thing.

[daehl]

This is so frustrating...

Today I'm trying to upgrade to ScriptMaster 2.0.5a, and I did everything I did previously to upgrade to ScriptMaster 2.0.3, but I cannot get the new plugin to load. I keep getting an "Error 474" message mailed to me from the Server.

I downloaded a fresh copy of ScriptMaster 2.0.5a.

I stopped my FMP server, and disabled the ScriptMaster 2.0.3 plugins.

I copied the 2.0.5a plugins into the appropriate folders:

/Library/FileMaker Server/Database Server/Extensions

/Library/FileMaker Server/Web Publishing/publishing-engine/wpc/Plugins/

I've use chmod command to fix their permissions

chmod g+wrx

and I used chown to correct their user/group ownerships

drwxrwxr-x 3 fmserver fmsadmin 102 Oct 14 09:31 360Works_ScriptMaster.fmplugin

But, all to no avail. Once I restart the server and try to enable the plugin I get an error 474 "Plug-in failed to load: 360Works_ScriptMaster.fmplugin" error.

The good news is, that I was able to quickly reverse the process and quickly revert to ScriptMaster 2.0.3 again.

So, has anyone been able to successfully load ScriptMaster 2.0.5a

I'm looking for tips or advice if so. Thanks!

Edited December 16, 2008 by Guest

[Jesse Barnum]

Daehl, it's working OK on our server as a database server plugin (ie. in /Library/FileMaker/Database Server/Extensions). What's your configuration (FM Server version, OS version), and are you installing this as a WPE plugin or a database server plugin?

[daehl]

Hi, Jesse.

My config is FileMaker Adv Server 9.0.3.325 on an iMac G5, 2GB RAM, 10.4.11, Java 1.5.0_16. I use ScriptMaster within databases hosted via IWP.

I am installing ScriptMaster in both the FMP server's "Extensions" and wpe's "Plugins" folder. I am replacing the ScriptMaster 2.0.3 plugins that are already installed and enabled there.

That's what is so odd, I've been using previous versions of ScriptMaster (currently 2.0.3) and they enable without problem.

I did have similar trouble a few months back when I upgraded to 2.0.3 (from 1.8.3) because I had problems setting the correct file owner for the plugins (I tried to set ownership using Finder's Get Info, but the changes didn't stick until I used 'sudo chown -R' instead). But that is not the problem this time.

ScriptMaster 2.0.3 is running well for me, except it occasionally stops responding in IWP. After reading the 2.0.5a changelog, I'm hoping that it will solve that.

I've re-downloaded 2.0.5a a few times, and they've all unzip'd fine, so I don't think the plugins are damaged or corrupted.

Is it possible there's a compatibility issue with my config above? I plan on trying a fresh install on an Intel iMac running 10.5, but it may be a fews days before I can get access to another computer to try. I'd rather not take my current server down for reinstallation if I don't have to. So I have reverted to ScriptMaster 2.0.3, which is generally working fine.

[daehl]

UPDATE- I was able to install and activate ScriptMaster 2.0.5a on another iMac running FMPAS 9.0.3.325. This time it was an Intel iMac running Mac OS 10.5.6. But, I'm not currently able to use that as my permanent FMP server. So, I still need to figure out why ScriptMaster 2.0.5a isn't working on an iMac G5 running 10.4.11.

Some of the likely culprits,

Is ScriptMaster 2.0.5a incompatible with an iMac G5?

Is it incompatible with Mac OS 10.4.11?

Is there something wrong with my config that allows ScriptMaster 2.0.3 to work, but not 2.0.5a?

I'm hoping the problem is one of the latter two, maybe I'll use some holiday downtime to do a clean install of 10.4.11 and/or 10.5.6 on another partition on my iMac G5 and see if that allows it to work.

[Jesse Barnum]

There was a build error in 2.05a that prevented ScriptMaster from working in Tiger. I do all my dev and testing on Leopard, so I didn't realize this - thanks for catching that. I've just posted 2.05b which fixes this problem.

[daehl]

There was a build error in 2.05a that prevented ScriptMaster from working in Tiger. I do all my dev and testing on Leopard, so I didn't realize this - thanks for catching that. I've just posted 2.05b which fixes this problem.

Thanks Jesse, I just downloaded and installed 2.05b, but unfortunately got the same result as with 2.05a. It will not activate and I get the dreaded error 474 email. And I've duplicated the results on two different iMac G5s running 10.4.11 and FMPAS 9.0.3.235

Have you definitely been able to get it working on Mac OS X 10.4.11 ?

The other thing I notice, is that with ScriptMaster 2.0.3, it shows a description of "Allows execution of interpreted java/groovy code. (2.03)" even before it's enabled. Whereas the 2.0.5x plugins display a description of "Not Loaded". It seems as if FileMaker Server just isn't able to read the contents of the plugin for some reason.