Log in to create and rate content, and to follow, bookmark, and share content with other members. Not a member? Join Now!

AnsweredAssumed Answered

How do we install the BaseElements plugin in FMS Windows Server 2008 R2?

Question asked by douglerner on Feb 25, 2018
Latest reply on Sep 7, 2018 by wimdecorte

Like • Show 0 Likes0
Comment • 28

A newbie question. I need to install BaseElements on my FMS 15 running under Windows Server 2008 R2.

Following the instructions on this page: https://www.filemaker.com/help/15/fms/en/index.html#page/fms/fmsh_plugins.14.3.html

I installed two copies of the 64-bit Windows plugin:

(1) In [drive]:\Program Files\FileMaker\FileMaker Server\Database Server\Extensions\

(2) In [drive]:\Program Files\FileMaker\FileMaker Server\Web Publishing\publishing-engine\cwpc\Plugins\

But no plugins show up at all in the Admin Console > Database Server > Server Plugins, even after I check the Enable FileMaker Script Engine (FMSE) to use plug-ins box.

What am I doing wrong?

Thanks,

doug

No one else has this question

Outcomes

28 Replies

user19752 Feb 25, 2018 10:31 PM
Mark Correct
Correct Answer
You'd need restarting FMS. (I tested with FMS16)
3 people found this helpful
Like • Show 1 Like1
Actions
douglerner @ user19752 on Feb 25, 2018 11:27 PM
Mark Correct
Correct Answer
user19752 wrote:

You'd need restarting FMS. (I tested with FMS16)
Are you sure? That seems a bit extreme.

On this page:
https://www.filemaker.com/help/15/fms/en/index.html#page/fms/config_dbserver_plugins.html
It says to Select Allow Install Plug-In File script step to install, update, and load Server plug-ins, but it doesn't mention restarting FMS.

But I just tried that and it didn't work either.

Also, after changing any settings in that tab I get locked out of the admin console > database server settings for several minutes.

Weird.
Like • Show 0 Likes0
Actions
monkeybreadsoftware @ douglerner on Feb 25, 2018 11:48 PM
Mark Correct
Correct Answer
Sometimes plugins show up alone, but sometimes we need to restart.
We usually start complaining if it does not show up after restarting!
Like • Show 1 Like1
Actions
douglerner @ monkeybreadsoftware on Feb 26, 2018 12:17 AM
Mark Correct
Correct Answer
Christian Schmitz wrote:

Sometimes plugins show up alone, but sometimes we need to restart.
We usually start complaining if it does not show up after restarting!
I just hate to attempt a restart because last time I did the database had to go through a long consistency check (like a half hour) before it came up.

I guess I could:

(1) close each database.
(2) do a restart in system services?
(3) then open up the databases

Maybe that will avoid the long consistency check because I will have closed down the databases first.

I wish there was a safe and simple FMS restart.

I wonder why the instructions don't say an FMS restart is needed while some other settings explicitly say it is.
Like • Show 0 Likes0
Actions
douglerner Feb 26, 2018 1:36 AM
Mark Correct
Correct Answer
Well, I went ahead and restarted the server (safely, after closing the databases). I had to restart it twice, because the first time the fmserver.exe process did not start. But the second time it did and everything opened ok. By closing the databases first I was able to avoid the long "database verification" step I sent through last time.

I don't know why I needed to restart it twice though.

Anyway, the BaseElements plugin is now showing as enabled.

Question - do I need to have both of those first two checkbox in the screenshot checked? The instructions were unclear. The first one seems obvious. The second one less so.

Thanks,

doug
Like • Show 0 Likes0
Actions
wimdecorte @ douglerner on Feb 26, 2018 4:19 AM
Mark Correct
Correct Answer
douglerner wrote:

I had to restart it twice, because the first time the fmserver.exe process did not start. But the second time it did and everything opened ok. By closing the databases first I was able to avoid the long "database verification" step I sent through last time.

I didn't see it mentioned before but when you use the FM script step "Install Plugin File" and you call it through PSoS you can avoid the manual manipulation and most of the time (depends on the plugin) you can avoid any restart. At least for the script engine plugin. Works like a charm with the BE plugin every time for me.

As to the quoted text: that would give me serious pause.
- it is not normal for fmsever.exe to fail to start
- you mention that closed the files first and that you in so doing avoided the long consistency check. Does that mean that the last time you restarted the machine without closing the files? And that the file ended up not closing in time before Windows rebooted the machine?

It is a long-standing best practice to always disconnect users and close the files before attempting to restart the FMS service or reboot the machine. Precisely for this reason. No point in taking chances.
But the fact that it didn't work on the restart combined with the fact that fmserver.exe fails to launch: that's pretty scary and I've only seen it happen on marginal machines or machines that otherwise have other things going on (running other tasks, failing hardware,...)
2 people found this helpful
Like • Show 0 Likes0
Actions
jfletch @ wimdecorte on Jun 3, 2018 12:01 AM
Mark Correct
Correct Answer
wimdecorte wrote:
I didn't see it mentioned before but when you use the FM script step "Install Plugin File" and you call it through PSoS you can avoid the manual manipulation and most of the time (depends on the plugin) you can avoid any restart. At least for the script engine plugin. Works like a charm with the BE plugin every time for me.
Well, it doesn't work for me either. The script step fails. Putting it into the folder manually does not get it to show up. Until I restarted the service in the Windows control panel. Then it works. So there is some other element to the install that some of us are not privy to. FMS 16.0.4 and WinServer 2016.
Like • Show 0 Likes0
Actions
wimdecorte @ jfletch on Jun 3, 2018 5:12 AM
Mark Correct
Correct Answer
Usually there would be one of two reasons:
- wrong version of the plugin (32-bit or mac/windows confusion)
- permissions on the FMS folders. That's normally not a problem on Windows, unless you condigured FMS to run as something different than "local system"?

Is FMS installed in the default "c:\program files"?
1 person found this helpful
Like • Show 1 Like1
Actions
user19752 @ jfletch on Jun 4, 2018 7:33 PM
Mark Correct
Correct Answer
I don't need restart on FMS17 WinServer2016.
And it can be done with PSOS.
The help is confusing that saying "to update", looks like "can't install new plug-in". If it is installed by copying file, should be enabled in admin console to work, but by the script it is enabled by default.
After
1.disable BE plugin on admin consle
2.fmsadmin stop fmse
3.delete plugin file from server folder
4.fmsadmin start fmse
5.use PSOS to install BE
then it worked again. BE is now enabled on admin console.

And the step use users' folder when run on client, but use server folder on PSOS. This mean the step manages server, not for the script session.
2 people found this helpful
Like • Show 2 Likes2
Actions
farm60 Aug 29, 2018 1:00 PM
Mark Correct
Correct Answer
I uploaded the BaseElements.fmx64 file to both folder locations (Extensions and Web Publishing) on the VM that houses FMS 16 as indicated in the instructions. After much restarting, the BaseElements plugin finally shows in the Server Plug-Ins tab in FMS, and both check boxes are also checked. However, both the Revert and Save buttons are grayed out at the bottom (not sure why - may not be an issue?). The FMS VM is a Windows unit, but clients are virtually all Macs accessing hosted files directly (not via WebDirect). I tried to write a small script to see if BaseElements functions are now available using FMP16 adv by setting $FileExists to the value of BE_FileExists(path), but Filemaker does not recognize this BE function (no BE functions show in right window). Could anyone take pity on this befuddled dbm, and help out? I'm lost!
Like • Show 0 Likes0
Actions
wimdecorte @ farm60 on Aug 29, 2018 1:47 PM
Mark Correct
Correct Answer
The easiest way to test if the plugin is installed is tun a script through PSoS and use the Get(InstalledPluginFiles) function and return its result. No need for anything fancy like trying to read from the disk itself.

The easiest way to install plugins on server and for the WPE is to use the "Install Plugin File" script step. Fire it through PSoS to install for FMSE and fire it through an XML/PHP API call or through WebDirect to install for WPE.

Obviously provided that FMS is configured to allow plugins and allow the 'install plugin file' script step.
1 person found this helpful
Like • Show 0 Likes0
Actions
farm60 Sep 4, 2018 11:14 AM
Mark Correct
Correct Answer
Thanks jrenfrew & wimdecorte for the feedback. The following is what I see on the FMS. It looks like BaseElements is attached on the server side. Then I generated two scripts as suggested. The first invokes a second PSOS script having only one command: Set Variable[$$GetPluginResult; Value: Get(InstalledFMPPlugins)]. The first script then uses a dialog to display the value of $$GetPluginResult. Unfortunately I don't see any value at all.

Not sure what I'm doing wrong. Any help would be much appreciated.

Paul
Like • Show 0 Likes0
Actions
wimdecorte @ farm60 on Sep 4, 2018 11:25 AM
Mark Correct
Correct Answer
farm60 wrote:

The first invokes a second PSOS script having only one command: Set Variable[$$GetPluginResult; Value: Get(InstalledFMPPlugins)]. The first script then uses a dialog to display the value of $$GetPluginResult. Unfortunately I don't see any value at all.
The issue is with the assumption around global variables. Those don't travel between your PSoS session and your local session. So your $$GetPluginResult locally will always be empty.

use a local variable and make the PSoS script pass the variable as a script result. The first script can then use Get(ScriptResult) and display that.
Like • Show 0 Likes0
Actions
farm60 @ wimdecorte on Sep 4, 2018 12:14 PM
Mark Correct
Correct Answer
Still no luck, probably because of my unfamiliarity with more advanced features. Here are my two revised scripts. The result is still null.

All the best,

Paul

Paul Farmer, PhD
Manager of Research Projects
Emory Vaccine Center
954 Gatewood Road
Atlanta, Georgia 30329
Work: 404-727-8598
Cell: 770-843-3957
pfarmer@emory.edu
Attachments
- image002.png44.6 KB
- image001.png63.7 KB
Like • Show 0 Likes0
Actions
jfletch @ farm60 on Sep 4, 2018 12:24 PM
Mark Correct
Correct Answer
Paul, set Wait for Completion in the PSoS step to ON in your calling script.
Like • Show 0 Likes0
Actions
farm60 @ jfletch on Sep 4, 2018 12:32 PM
Mark Correct
Correct Answer
Ah, success!!! Can’t thank you all enough. I’ve learned a few valuable lessons here. Guess training an ole dog is still feasible!

All the best,

Paul

Paul Farmer, PhD
Manager of Research Projects
Emory Vaccine Center
954 Gatewood Road
Atlanta, Georgia 30329
Work: 404-727-8598
Cell: 770-843-3957
pfarmer@emory.edu
Like • Show 0 Likes0
Actions
jfletch @ farm60 on Sep 4, 2018 12:36 PM
Mark Correct
Correct Answer
I HOPE training an old dog is still feasible. Otherwise I should just give up. ::-)
Like • Show 0 Likes0
Actions
farm60 Sep 5, 2018 6:22 AM
Mark Correct
Correct Answer
Mea culpa. Now that the plugin is installed in both locations in FMS, it is not clear how to actually use BaseElements functions because they don't seem to be available from within FMP Adv scripts on the client Mac when running a hosted solution. Is it necessary to also download BaseElements FileMaker files and somehow link them to my solution? I can't decide if my issues are due to my ignorance or instead to a lack of information on the web indicating how to initially set up access to BaseElements functions.
Like • Show 1 Like1
Actions
wimdecorte @ farm60 on Sep 5, 2018 6:26 AM
Mark Correct
Correct Answer
Yes, to develop a script that uses the functions of the plugin, but that will be executed through PSoS or a schedule (and thus use the actual plugin on the server), you need to have a local copy of the plugin on your dev machine.

The plugin functions are the same for Mac or Windows so it doesn't matter that your server is Windows and you develop on a Mac.
1 person found this helpful
Like • Show 0 Likes0
Actions
farm60 Sep 5, 2018 9:12 AM
Mark Correct
Correct Answer
I think it may be time to give up. I downloaded the Mac 16 version of the BaseElements software which when decompressed gives an instruction file and the app. Instructions say to create a Database Design Report using the XML option, to close one's solution, to open BaseElements, and then to click the 'Import New' button. Unfortunately I get the following message. The client is running FMP Adv 16 and the hosted file is accessed using FMS 16. Since I downloaded the BaseElements 16 zip file and the .dmg file for the Mac, I don't know what the problem might be since presumably the downloads match the client and server software. I was originally excited about using BaseElements, but trying to install it has been a pain and I'm beginning to lose hope.
Like • Show 0 Likes0
Actions
wimdecorte @ farm60 on Sep 5, 2018 9:17 AM
Mark Correct
Correct Answer
You didn't download the BaseElements plugin, you downloaded Baselements the analysis tool...

What you need is here: BaseElements Plugin – BaseElements Plugin Help Centre
Like • Show 0 Likes0
Actions
techt @ farm60 on Sep 5, 2018 9:19 AM
Mark Correct
Correct Answer
This reads to me like a separate question. There is the BaseElements plugin, and there is the BaseElements FM app. I tried a few times to install the three files for the app on the server and never could get it to behave properly, so I'm just running it locally as I have for years. Yes, create the XML from the developer menu, you don't need to close that file afterwards. You need to keep all of the BaseElements files in a single folder so it doesn't have to search for them. I couldn't read your error image that you uploaded, so I'm unsure of the error you're seeing. Once imported, BaseElements does a great job of examining your file(s) and letting you know where there may be issues.

HTH
Like • Show 0 Likes0
Actions
farm60 Sep 5, 2018 11:37 AM
Mark Correct
Correct Answer
I finally managed to get the BaseElements file to run locally and it showed lots of errors in my two linked databases, virtually all of which were not critical and had no impact on functions. I will likely eliminate them when time permits. However, the reason for wanting to try BaseElements was to use the new functions from within my solution, especially the one that tells if a file/folder is available. Unfortunately I still don't have a clue about how to do this. In my naive world as an intermediate FM developer, I thought once you added the plugin to the two folders on the FMS (extensions and web pub) that you could then run a hosted database using the FM Adv client and new functions would magically appear when using scripts. I would humbly suggest that if a goal is to have developers evaluate BaseElements and then pay for its features, that there should be an explicit set of comprehensive instructions on how to set up this software. I would be happy to pay for it, but not if I have to struggle for hours trying to figure out how to do it. Sorry for being blunt and hope I haven't offended anyone.
Like • Show 0 Likes0
Actions
techt @ farm60 on Sep 5, 2018 11:47 AM
Mark Correct
Correct Answer
To use BE in your solutions, you need to install the plugin on your computer, even if the solution is hosted. You would only need it on the server if the server needed it to run a script (PSOS).
Like • Show 0 Likes0
Actions
wimdecorte @ farm60 on Sep 5, 2018 11:50 AM
Mark Correct
Correct Answer
farm60 wrote:

I finally managed to get the BaseElements file to run locally and it showed lots of errors in my two linked databases, [...]
However, the reason for wanting to try BaseElements was to use the new functions from within my solution, especially the one that tells if a file/folder is available.

You're still mixing up the BaseElements analysis tool and the BaseElements plugin. One has nothing to do with the other. To use the plugin functions you just download and install the plugin from the link I provided. The Analysis tool is great and provides lots of insights into your solution but it is not what you are after at this point.
1 person found this helpful
Like • Show 0 Likes0
Actions
farm60 @ wimdecorte on Sep 5, 2018 12:25 PM
Mark Correct
Correct Answer
Ah, it now works thanks to your great patience! Thank you so much!!!

All the best,

Paul

Paul Farmer, PhD
Manager of Research Projects
Emory Vaccine Center
954 Gatewood Road
Atlanta, Georgia 30329
Work: 404-727-8598
Cell: 770-843-3957
pfarmer@emory.edu
Like • Show 0 Likes0
Actions
farm60 Sep 7, 2018 7:07 AM
Mark Correct
Correct Answer
I spoke too soon. The plugin file was added to the FMS in the two folders suggested in the instructions and also on the client so that BE functions are now visible when coding within a script. However, I can't get any of the functions to actually work whether running a script locally or from PSOS. Here is the latest attempt using the PSOS approach. It doesn't work if I instead try to confirm the present of a file on this HD. This really shouldn't be so hard.

Script 1:
Perform Script on Server [Wait for completion: On; "Script 2"]
Show Custom Dialog [$FileExists; "The result of this BE_FileExists function is: " & $FileExists]

Script2:
Set Variable [$FileExists; Value: BE_FileExists ("/Macintosh HD")]
Exit Script [ Text Result: $FileExists ]
Like • Show 0 Likes0
Actions
wimdecorte @ farm60 on Sep 7, 2018 7:17 AM
Mark Correct
Correct Answer
It really isn't that hard... but don't try to confirm the presence of the plugin like this.

Use the Get() function to have the PSoS session report what plugins are installed, part of the info you'll get is also whether the plugin is enabled. That's the actual relevant information.

When installing plugins on server, also use PSoS with the "install plugin file" script step. That way you'll get an error if it does not work *AND* you'll be certain that FMS puts the plugin in the right place.

I typically create a "call log" table in my solutions where the PSoS calls will create a record and log relevant data, like the available plugins, start and end time,... things that will help me troubleshoot.
1 person found this helpful
Like • Show 1 Like1
Actions

How do we install the BaseElements plugin in FMS Windows Server 2008 R2?

Outcomes

Attachments

Related Content

Recommended Content