Digging into the event viewer the problem was caused by an automatic Java update to Java 7 Update 65.
Digging into the event viewer the problem was caused by an automatic
Java update to Java 7 Update 65.
Great. Java is up-to-date and the servers are down.
Don't let anyone or anything make changes to your server without your
full approval. Just don't do it. In this case, you allowed Oracle's
robots to modify your servers. Why? Your servers were working before the
robots started work and they didn't work when the robots had finished.
Now you have three good reasons never to let Oracle do your system
At this point we are still trying to get our servers back up and running. We haven't begun to investigate how Java updated. In fact two of the servers that went down are dev and testing servers. All patches are tested on them before installing on the live server.
We found the culprit. Kaspersky Antivirus 8.0 for Windows Server Enterprise has an option to patch known security risks. Even though this option is turned off on our FileMaker servers, Kaspersky installed the update anyway.