Skip to content

Permissions and SQL Errors

Check the actual FileMaker error before changing permissions.

  • Symptoms: Could not fetch tables, FileMaker SQL - Error 825(), or the Metadata Explorer is empty.
  • Cause: FileMaker reports that one file is not authorized to reference a protected file. An empty Metadata Explorer alone does not establish this cause.

The fmplugin privilege controls certain plug-in operations between files, including SQL and script execution. It is not a blanket requirement for reading metadata from the current file. FileMaker still enforces the account’s access rights. See Claris: controlling plug-in access between files.

Some macOS Genie versions display an Enable fmplugin banner before trying the read. That banner alone is not a FileMaker permission denial. Contact support for the corrected metadata-refresh build; no helper script is required.

805Error.png

Ask your FileMaker administrator to check the source and target files and their authorization. If cross-file plug-in access is intended, the administrator can authorize the files or configure an appropriate fmplugin or plug-in-specific privilege. Do not grant Full Access just to load metadata.

If the administrator chooses to enable fmplugin, use these steps:

  1. Go to File > Manage > Security…
  2. Click on the Advanced Settings… button.
  3. Select the Extended Privileges tab.
  4. Scroll down to find the keyword fmplugin. Click to edit.
  5. In the Privilege Sets list, select only the privilege sets intended to receive this access.
  6. Click OK to save all changes.
  7. Refresh metadata in Genie and check whether the actual SQL error is resolved.

Step 1: Open Security Management NavigateToSecurity.png

Step 2: Find Extended Privileges ExtendedPrivileges.png

Step 3: Enable fmplugin ScrollToFMPlugin.png

Step 4: Assign to your Privilege Set UpdatePrivilege.png