So last week I spun up a Microsoft Azure VM to test FMS 17 and it was working well. Last night started migrating our second server and all was good. One of the final things was to install ScriptMaster. Didn't work and stupidly didn't test it last week. Had to roll back to FMS 16 and wasted several hours of work (my mistake for lack of QA)!

Today I tried it again on a new VM and could reproduce the issue so it's not specific to our build.

Here's what I did to reproduce the issue:

1. Create an Azure VM running Server 2016.
2. Change the language to UK.
3. Install FMS 17.
4. Install Web Sockets (an issue my Colleague sussed out here).
5. Copy the ScriptMaster Plugin into the Extensions folder and try to enable it.

I got the following events in the FMS log:

Quote

Error    474    Test    Plug-in failed to load: 360Works_ScriptMaster.fmx64
Error    701    Test    FileMaker Script Engine process has terminated abnormally.

Additionally the Event Viewer had two events - A 701 error with the same description as above and the following:

Quote

Error 1000, Application Error:

Faulting application name: fmsase.exe, version: 17.0.1.146, time stamp: 0x5acd4b65
Faulting module name: ucrtbase.dll, version: 10.0.14393.2097, time stamp: 0x5a820a13
Exception code: 0xc0000409
Fault offset: 0x000000000006eabe
Faulting process ID: 0x11a0
Faulting application path: C:\Program Files\FileMaker\FileMaker Server\Database Server\fmsase.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll

Hope this gets sorted soon as I need to roll out FMS 17 :(.

We just posted a new version of ScriptMaster about an hour ago - version 5.1. I think that will fix the problem; please give it a shot and let me know if that resolves the issue.

That seems to have fixed the problem on my test server, and I'll try it again on our production server in the next few days. Pity this wasn't released a day or two ago 😯.

Thanks for the quick turnaround!

Thank Jesse...