AnsweredAssumed Answered

Oh FMSE, oh FMSE, how convoluted are thy behaviours

Question asked by StephenWonfor on Dec 12, 2018
Latest reply on Feb 12, 2019 by StephenWonfor



Gathering a few threads on this topic into this one - perhaps to make a toque to cover up this annoying mess.


The plot:

5 clients with their own in-house FMServers.

Box 1 FMS16.0.4 on OSX 12.4

Box 2 FMS16.0.4 on OSX 12.4

Box 3 FMS16.0.4 on Windows Server 2016

Box 4 FMS16.0.4 on Windows Server 2012

Box 5 FMS16.0.4 on OSX 13.6.

Boxes 1 and 3 are suffering from either or both of "ghost connections" or the FMSE (Filemaker Script Engine) suddenly quitting. Box 1 even reports, at times ( roughly 14 day intervals), that "FileMaker Server is now awake. All schedules will now be resumed." - even though every known energy saver setting is OFF. I have read of this happening way back in FMS 11. Box 4 suffered from ghosts and FMSE issues after upgrade from FMS 14 to 16 - rebuilding all serverside scripts seemed to fix it - gets ghosts perhaps fortnightly now. Box 3 is getting FMSE suddenly OFF after 6 months of quiet. Wow, rather sounds like describing a group of different volcanos and their eruptive states!




Reboot the machine, stop/start the FMSE, rebuild all server scripts.

Also looking to find some code that we can call via CRON or TaskScheduler that would stop/start the FMSE, maybe disconnect ghosts, maybe close dbs and reboot server.



For those who have ventured up to FMS 17 - does this sort of "inconvenience" still occur there? How are things in the Cloud?



"Beware of bugs in the above code; I have only proved it correct, not tried it." - Donald E. Knuth.


Ghosts illustrated