Troubleshooting Common MBS FileMaker Plugin Issues

Troubleshooting Common MBS FileMaker Plugin Issues

If the MBS FileMaker Plugin is causing errors or unexpected behavior, follow this step-by-step troubleshooting guide to identify and resolve the most frequent problems quickly.

1. Verify plugin installation and version

• Check plugin location: Ensure the plugin file (e.g., MBSFMPlugin.bundle on macOS or MBSFMPlugin.dll on Windows) is placed in FileMaker’s Extensions/Plugins folder:
  • macOS: /Library/Application Support/FileMaker/Plugins or ~/Library/Application Support/FileMaker/Plugins
  • Windows: C:\Program Files\FileMaker\Plugins or C:\Users\AppData\Local\FileMaker\Plugins
• Confirm plugin is enabled: In FileMaker, go to Help > About Plugins (or File > Manage > External Data Sources/Plugins depending on version) and verify MBS appears in the list and shows as enabled.
• Version compatibility: Ensure the plugin version is compatible with your FileMaker and OS versions. Update to the latest stable MBS plugin release if needed.

2. Check licensing and registration

• License file: If you use a licensed build, confirm the license file or registration key is correctly installed.
• Trial limitations: Some functions may be disabled or limited in trial mode—verify you’re not hitting trial restrictions.
• Restart FileMaker: After updating license information, restart FileMaker to ensure registration takes effect.

3. Confirm function names and parameters

• Exact function names: MBS functions are case-sensitive in some contexts—use the exact names shown in the MBS function reference.
• Parameter order and types: Review the MBS documentation for required parameters and data types. Incorrect parameter types commonly cause errors.
• Use the Function Browser: Open FileMaker’s calculation dialog and use the plugin’s function list (if available) to insert functions to avoid typos.

4. Inspect error codes and messages

• Capture plugin errors: Use Get(LastError) after plugin calls; MBS often returns plugin-specific error codes—look these up in the MBS documentation.
• Enable plugin logging: Many MBS functions and the plugin itself support verbose logging. Turn on logging to produce detailed output (check MBS docs for the exact functions or script steps to enable logs).
• Interpret common codes:
  • File/IO errors — check file paths, permissions, and that the files exist.
  • Network errors — verify hostnames, ports, protocols, and firewall access.
  • Authentication errors — confirm credentials and any required encryption settings.

5. File paths, permissions, and sandboxing

• Absolute vs. relative paths: Use absolute paths where possible. For cross-platform solutions, verify path formats (macOS vs. Windows).
• FileMaker sandbox (macOS): If using FileMaker Pro with macOS