Common issues

Note: this common issues apply to plugins released prior to May 2017

Troubleshooting Java on Windows

In most cases 32-bit Java is required on Windows, these days most machines are 64-bit and users generally use 64-bit browsers this leads to 64-bit Java installed on most system since users arrive to java.com using 64 bit browsers.

To verify that you have 32-bit java installed you will need to open the 32-bit command prompt.

Instructions:

1. Click Start.
2. Type %windir%\SysWoW64\cmd.exe in Start Search box.

Once the command prompt is up type: java -version

You should get the version of the installed 32-bit java.

Webviewer is black or has Red X

This happens because Java now requires the same jars for applets as it does for webstart. All 360Works plugins had to be redeployed to comply with this. The solution is to use the latest version of the all 360Works plugins.

Unsupported class version

This can happen on Leopard if /System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK is symlinked to 1.6 instead of 1.5 as on most systems. This is a problem because Java 6 on Leopard is 64-bit and FileMaker is a 32-bit application. Update all 360Works plugins to the latest version.

Re-Enabling Java 6 on OS X 10.7 Lion

If, after installing Java for OS X 2012-006 and Java 7, you want to disable Java 7 and re-enable the Apple-provided Java SE 6 plug-in, follow these steps.

Note: You must be logged in as an adminstrator.

Note: If prompted for your administrator password after a command, enter it and then press the Return or Enter key.

Open Terminal, located in the Utilities folder. Enter this command, then press the Return or Enter key:

sudo mkdir -p /Library/Internet\ Plug-Ins/disabled

Enter this command, then press the Return or Enter key:

sudo mv /Library/Internet\ Plug-Ins/JavaAppletPlugin.plugin /Library/Internet\ Plug-Ins/disabled

Enter this command, then press the Return or Enter key:

sudo ln -sf /System/Library/Java/Support/Deploy.bundle/Contents/Resources/JavaPlugin2_NPAPI.plugin /Library/Internet\ Plug-Ins/JavaAppletPlugin.plugin

To re-enable Java SE 6 Web Start, enter this command, then press the Return or Enter key:

sudo ln -sf /System/Library/Frameworks/JavaVM.framework/Commands/javaws /usr/bin/javaws

Additional Information The following steps will undo the above commands and restore Java 7.

To disable Java SE 6 Web Start opening

Enter this command, then press the Return or Enter key:

sudo ln -sf /System/Library/Frameworks/JavaVM.framework/Versions/Current/Commands/javaws /usr/bin/javaws
 

When prompted, enter your administrator password, then press the Return or Enter key.

To re-enable the Java 7 applet plug-in

Download and re-install the Oracle Java 7 JRE from this website: http://www.oracle.com/technetwork/java/javase/downloads/jre7-downloads-1637588.html.

via http://support.apple.com/kb/HT5559?viewlocale=en_US

FileMaker crashes with 360Works plugins installed On Windows

This can happen if you are using plugins that have different framework. Our plugins were updated in Dec 2014 with a new framework and using plugins prior to that date with ones post will cause issue. The first step is to make sure that all of your plugins are up to date.

This can also happen in FileMaker 14+ due to FileMaker creating a registry record that causes the crash. To resolve this, open regedit.exe (registry editor) and navigate to "HKEY_CURRENT_USER/Software/FileMaker/FileMaker Pro/15.0A/Plugins" and check for a record called "disabled". If it exists, delete it. You will need to change the "15.0A" to reflect the version of FileMaker you are using.

Plugins Do Not Enable of Mac

This first thing to check is to make sure that you have Java 6 installed. All 360Works plugins currently require Java 6 when installing on Mac OS. Next, make sure that all of your plugins are up-to-date. The reason for this is we have changed framework in the past and plugins with old framework are not compatible with new framework plugins. We also have made changes for specific version of FileMaker Pro so staying update to date is essential. Be sure to check all three extension folders for old plugins. We have also seen problems with plugins initializing because of special characters in the file path to the plugin. For example if your hard drive is named Macintosh HD [DMZ] then the [] in the file path will cause the plugin to not initialize due to an invalid file path. Removing the special characters will allow the plugin to initialize.