FM Crashing when plugins loaded

[tv_kid]

I'm having some issues with one particular computer at a client (all others are ok).

 

FMP12

Windows 7 (64-bit)

Plugins (installed in Users AppData folder):

• 360Works_Email
• 360Works_ScriptMaster (latest version)
• SuperContainerCompanionPlugin (latest version)

 

When FMP is launched, the ScriptMaster and SC_Companion plugins are not enabled.  Enabling them causes the application to crash.

 

Java version is 1.7, 32-bit.

 

I've tried trashing the 360Works folder in the users documents folder, but this didn't change anything.

 

Any ideas?

 

Matt

[Joe Pampalon]

Hi Matt,

 

Can you list the specific version numbers of the 360Works plugins you are using? You can find this information by going to the FileMaker Pro Preferences > PlugIns tab and selecting (not checking) each plugin.

[tv_kid]

Hi Joe

 

Thanks for replying.  

 

The version numbers are:

• Email - 1.963
• ScriptMaster - 4.206 (latest version downloaded today)
• SC Companion - 2.896 (latest version downloaded today)

 

Regards

 

Matt

[Joe Pampalon]

Hi Matt,

 

I believe you are seeing a compatibility issue involving plugins built before June 2013 and plugins built after. In June 2013, we made a compatibility fix for Java 7 update 25 (and Java 6 update 45) that causes a conflict with older plugins. The Email plugin you have was built before this compatibility fix, so I believe it is causing the conflict.

 

An easy test is to disable the Email plugin, restart FileMaker Pro, then try to enable the ScriptMaster and SuperContainer Companion plugins. If I'm right, they should load fine.

 

You can get an updated build of Email v1 by going to http://360works.com/email-plugin/ and clicking the "Buy Now" button. This will take you to a new page with a "1.973" link at the top. Once you install that, all the plugins should run alongside one another without issue.

[tv_kid]

Hi Joe

 

Thanks for following up, for some reason I didn't get a notification.

 

I'll try your suggestion with the Email plugin and see if that fixes it.  Interesting that no other users are affected, I guess they must have an older version of Java installed...?

 

Matt