1 Reply Latest reply on Jul 14, 2016 11:52 AM by psuchad

    File has been forcefully disconnected by the host

    jeffp1

      File has been forcefully disconnected by the host. All affected windows will be closed. [From Administrator: ""]

       

      Filemaker Pro 14.0v6

       

      Hello all,

      We are getting this error message several times a day.  We have a simple filemaker db shared file that two other computers connect to.  This problem started after upgrading the computers to Win10 (from Win7).  We have verified the network adapters are set to not go to sleep or anything similar.  No other network issues that we can find.  Nothing appears in the Windows Event Viewer when the file crashes.  Another dept at our company uses a similar setup and theirs works fine.

       

      Any ideas how to resolve this would be greatly appreciated.

      Thanks!

      - Jeff

        • 1. Re: File has been forcefully disconnected by the host
          psuchad

          Having the same problem for a month now. Random clients are disconnected every 5-30 minutes. Server logs "Client no longer responding, connection closed. (10)"

           

          We have tried moving servers to a new VM, moving VM to a new physical server, moved switches, installed completely new servers. The problem is now happening to three different servers using two FileMaker Server versions (13 and 15).

           

          Clients disconnecting are physical machines, virtual machines, remote desktop connections using Windows 7, 8, and 10. A physical machine can have a connection to the hosted file at the same time as a virtual machine running on the same physical machine. Virtual machine will disconnect without the physical machine disconnecting.

           

          Sniffing packets show that the FileMaker server will send a transmission to the client, the client will respond, the server sends a retransmission, then sends a disconnect.

           

          There is no latency or server performance issues that we can see. It just seems like the FM server is not seeing the client acknowledgements.