We just completed a round of Windows updates (yay!) and now our two FileMaker servers are becoming unstable after a few hours of being started up. For the most part, the databases remain available but the admin service continuously crashes and a server script we have to import from an SQL database on one of the servers ends up timing out.
Immediately preceding the admin process constantly crashing are the following two events in the Windows Application log:
- A request to allocate an ephemeral port number from the global TCP port space has failed due to all such ports being in use.
- TCP/IP failed to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint. This error typically occurs when outgoing connections are opened and closed at a high rate, causing all available local ports to be used and forcing TCP/IP to reuse a local port for an outgoing connection. To minimize the risk of data corruption, the TCP/IP standard requires a minimum time period to elapse between successive connections from a given local endpoint to a given remote endpoint.
Running the command "netstat -b" from the command line spits out a huge string of connections that takes a good 30 seconds to get through. On a normally running system it's done in a few seconds and shows about a hundred connections (from past experience running this command). The most frequent processes with connections scrolling past are:
Has anyone else seen this, and more importantly how do I make it stop crashing?
Potentially culprit updates (will soon be attempting uninstall of * ones that are showing up in the uninstall list):
*2018-06 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4284880)
Windows Malicious Software Removal Tool x64 - June 2018 (KB890830)
2018-05 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4103723)
*2018-05 Update for Windows Server 2016 for x64-based Systems (KB4132216)