Our office recently replaced a database server and upgraded to FMS17 from FMS16. Now that FMS17 is being used, the Script Engine process terminates abnormally when 2 scheduled scripts using the Email plugin fire-off at the same time. Individually, the scripts run fine. However, run in tandem, they crash FMSE. Any thoughts on why the  360Works Email plugin would allow simultaneous scripts to run in FMS16 but not in FMS17? 

Server Version is: 17.0.2.203
Plugin Version is: 3.1

Sample Event Logs:
2019-03-21 17:35:00.166 -0600    Information    148    SERVERNAME    Schedule "Email Example A" running.
2019-03-21 17:35:00.166 -0600    Information    689    SERVERNAME    Schedule "Email Example A" has started FileMaker script "MyScriptA".
2019-03-21 17:35:00.166 -0600    Information    148    SERVERNAME    Schedule "Email Example B" running.
2019-03-21 17:35:00.166 -0600    Information    689    SERVERNAME    Schedule "Email Example B" has started FileMaker script "MyScriptB".
2019-03-21 17:35:11.371 -0600    Information    645    SERVERNAME    Schedule "Email Example B" scripting error (1636) at "MyFile : MyScriptB : 26 : Send Mail".
2019-03-21 17:35:12.074 -0600    Error    701    SERVERNAME    FileMaker Script Engine process has terminated abnormally.
2019-03-21 17:35:12.090 -0600    Error    757    SERVERNAME    Schedule "Email Example B" aborted; FileMaker scripts can't be run because FileMaker Script Engine (FMSE) process is stopped. Use the command "fmsadmin start fmse" to start the FMSE process.
2019-03-21 17:35:12.090 -0600    Information    126    SERVERNAME    Schedule "Email Example B" scheduled for 03/21/2019 05:45 PM.
2019-03-21 17:35:12.090 -0600    Error    757    SERVERNAME    Schedule "Email Example A" aborted; FileMaker scripts can't be run because FileMaker Script Engine (FMSE) process is stopped. Use the command "fmsadmin start fmse" to start the FMSE process.
2019-03-21 17:35:12.090 -0600    Information    126    SERVERNAME    Schedule "Email Example A" scheduled for 03/22/2019 05:35 PM.
2019-03-21 17:35:14.231 -0600    Warning    30    SERVERNAME    Client "Email Example A (FileMaker Script)" no longer responding; connection closed. (10)
2019-03-21 17:35:25.452 -0600    Information    703    SERVERNAME    Starting FileMaker Script Engine process...

Edited March 22, 20196 yr by mat101010

A power outage and UPS failure caused the Windows 2016 server to restart. For unknown reasons, this appears to have resolved the problem. The server had been intentionally restarted once while experiencing the above issue.  I confirmed in the Event log that the same scripts are firing at the same time and FMSE is not terminating abnormally. 

...I guess 'have you tried turning it off and back on' would have been the correct response to this problem. Ugh.