FileMaker Pro intermittently hangs on plugin startup (Windows)

[Mattk]

I'm having intermittent issues with FileMaker Pro 16.0.3 on several Windows 10 workstations that I think is due to ScriptMaster not starting up properly when FileMaker starts. When the startup hangs, no FileMaker windows show up and I have to kill the FileMaker process through Task Manager to try starting up the program again. Eventually the program will startup without any changes being made to the system.

The log file 360Plugins_FMPro.log in c:\Users\<user>\360works shows this when the startup hangs and it never updates:

(C++ Tue Jan 02 14:20:02 2018) INIT - Creating new log file
(C++ Tue Jan 02 14:20:02 2018)  *** INIT for 360Works ScriptMaster_FMPro at Tue Jan 02 14:20:02 2018, headless mode 0, appTypeShort 1, JaCK version 2.0
(C++ Tue Jan 02 14:20:02 2018) Read JVM Version from registry: 1.8
(C++ Tue Jan 02 14:20:02 2018) Found JVM dll at C:\Program Files (x86)\Java\jre1.8.0_152\bin\client\jvm.dll
(C++ Tue Jan 02 14:20:02 2018) No existing JVM found; creating one.
(C++ Tue Jan 02 14:20:02 2018) 0: -Djava.class.path=noclasspath
(C++ Tue Jan 02 14:20:02 2018) 1: -Djava.net.preferIPv4Stack=true
(C++ Tue Jan 02 14:20:02 2018) 2: -Djsse.enableSNIExtension=false
(C++ Tue Jan 02 14:20:02 2018) 3: vfprintf
(C++ Tue Jan 02 14:20:02 2018) 4: -Xbootclasspath/a:C:\Program Files (x86)\Java\jre1.8.0_152\lib\deploy.jar;C:\Program Files (x86)\Java\jre1.8.0_152\lib\plugin.jar;C:\Program Files (x86)\Java\jre1.8.0_152\lib\javaws.jar
(C++ Tue Jan 02 14:20:02 2018) 5: -Djava.ext.dirs=C:\Program Files (x86)\Java\jre1.8.0_152\lib;C:\Program Files (x86)\Java\jre1.8.0_152\lib\ext;C:\windows\Sun\Java\lib\ext

I referred to the common issues wiki page and saw that C:\ProgramData\360Works\Plug-ins\jre\1.8.0_121 was missing on my systems. It seems like the plugin was using the system-wide Java install (1.8.0_152). I manually downloaded JRE and put it in place following the wiki instructions, but still get the issue intermittently.

I noticed in the 360Plugins_FMPro.log that the system-wide JRE install (C:\Program Files (x86)\Java\jre1.8.0_152) is still being used rather than the one in C:\ProgramData\360Works... could that be the issue?

A bit more info on the systems:

• All systems are 64bit Windows 10
• ScriptMaster is the current version (5.07)
• The issue happens on systems running FileMaker Pro 32-bit and 64-bit.
• The version of Java installed is the same 'bit' as the version of FileMaker (i.e. 32-bit FMP has 32-bit Java and 64-bit FMP has 64-bit Java installed).
• The issue happens during initial FileMaker startup, before I open a DB.

Thanks for any assistance!

Matt

[Mattk]

Ack- I was wrong ScriptMaster was an old version!    I'll update the thread if the problem persists.