Common Plugin Issues
Table of Contents:
Common Plugin Issues
Plugins not showing up in macOS
The 360Works Team has received reports from customers running very old versions of our plug-ins on macOS that the plug-ins have suddenly stopped working and appearing in Preferences>Settings. We have determined that this is due to Apple revoking an obsolete 360Works code signing certificate that has not been in use for years. Unfortunately, this means that older versions of our plugins will no longer work in macOS in environments where code signing and notarization are required.
If you find yourself in this situation, with old 360Works plug-ins no longer working on macOS, here are your options:
For these plug-ins, you can purchase an upgrade to the latest version, or download and install an older version which still functions correctly:
| Plugin | Latest Version | Older Version |
|---|---|---|
| Charts | Upgrade to latest | v2.3 |
| Upgrade to latest | v4.11 | |
| FTPeek | Upgrade to latest | v3.2 |
| JDBC | Upgrade to latest | v2.3 |
| Plastic | Upgrade to latest | v3.3 |
| RemoteScripter | Upgrade to latest | v2.3 |
| Web Assistant | Upgrade to latest | v2.3 |
| SuperContainer | Upgrade to latest | v2.954 |
| 360Deploy | Upgrade to latest | v2.86 |
| ScriptMaster | Upgrade to latest (free) | — |
For Scribe, make sure you have a current maintenance license with 360Works, then download and install the newest major version. If maintenance on your license has been expired for longer than 3 years, you will need to purchase a new license as it would be equivalent to the cost to bring to current. You can check your maintenance status here.
For ScriptMaster-generated or custom-built plugins that have stopped working, please reach out to us as the plugins will need to be rebuilt.
MirrorSync, Zulu, and SafetyNet are unaffected by this issue, as are all plug-ins on the Windows and Linux platforms.
Plugins released on or after May 2017 fail to load
Upon first initialization, the plugins will download support files that are necessary for operation. If this process fails for whatever reason (permissions, network issues, firewalls, etc.) then the plugins will fail to enable. You can manually do this process. It varies depending on whether you are in Mac or Windows.
This may appear as the error: "An error occurred while downloading https://download.360works.com/jre/win/1.8.0_121.zip. Couldn't connect to server"
For Mac
Note: Since the Gatekeeper utility in macOS is pretty restrictive, it is recommended that you allow the plugin to download and set up the JRE to avoid files getting quarantined by GateKeeper. Most enabling issues can be resolved by deleting the 360Works folder (paths shown below) and then attempting to enable the plugin. This causes the plugin to re-download the required JRE. If this fails and/or you have network restrictions that will not allow the plugin to download the JRE, you will more than likely need to complete the process manually. In this case, follow the instructions below.
Download the support files here.
For FileMaker Pro
- Open Finder and navigate to
/Users/USERNAME/Library/ApplicationSupport and look for a 360Works folder. If it exists, delete it and recreate it. If it does not exist, create it. - Create two folders inside the 360Works folder so that the path is
/Users/USERNAME/Library/Application Support/360Works/Plug-ins/jre - Extract the downloaded files inside the jre folder.
- Open Terminal and run the following command
sudo xattr -r -d com.apple.quarantine /Users/USERNAME/Library/Application Support/360Works/Plug-ins/jre - Launch FileMaker Pro and check in
Preferences->Pluginsthat the plugin is enabled. You may need to check it to enable it.
For FileMaker Server
- Open Finder and navigate to
/Library/FileMaker Server/Library/Application Support/and look for a 360Works folder. If it exists, delete it and recreate it. If it does not exist, create it. - Create two folders inside the 360Works folder so that the path is
/Library/FileMaker Server/Library/Application Support/360Works/Plug-ins/jre - Extract the downloaded files inside the jre folder.
- Open Terminal and run the following command
sudo xattr -r -d com.apple.quarantine /Library/FileMaker Server/Library/Application Support/360Works/Plug-ins/jre - Restart the FMSE and check in the admin console that the plugin shows as enabled. You may need to check it to enable it.
Windows plugins released after 1/21/2018
These plugins use an environment variable to determine where to save the support files and also use updated support files.
Download 64-bit support files here.
Download 32-bit support files here.
Open Windows Explorer and type %LocalAppData% into the address bar. Look for a 360Works folder, if it does not exist create the structure 360Works/Plug-ins/jre. Extract the zip file in the "jre" folder so that it matches the screenshot below.
