Could it be that the Windows patching process does not finish on those machines and does not reboot the machine? That would explain it but there would have to be some evidence that some of the patches did not complete.
The FMS service itself is set to auto-start, correct? And they are all running under the default of "local system" or were they assigned some sort of service account?
Thanks for this. I believe the machines are restarting. Which log might I look at to see if the patch process didn't finish?
The FileMaker Server service is set to auto-start. I will check the account that these machines are assigned, though I believe a few of them are just standard installations.
1 of 1 people found this helpful
The system event log would be the one that I turn to, but I would assume that the application event log has it too.
Also check the hardware specs on those rogue server, are any of those minimal or running low on disk space? Could be timing issues that way.
Turns out disk space is not an issue.
I will check the sys logs on the next failed restart.
Thanks for your help.