3 Replies Latest reply on Jan 24, 2017 4:24 PM by ADNPlus

    Users are being disconnected from FileMaker server

    jgould81

      Been searching for answer to this problem, but have been unsuccessful up to now.

       

      We recently migrated a client of ours to a new Windows Server 2012 R2 server to host FileMaker.  Since the migration staff have reported being disconnected often from FileMaker server.  Our client uses FileMaker to use a series of database files created by Shopworx

       

      We've taken a few steps with heir support to attempt to solve the problem.

      1. Using only the version of Java distributed with the product, version 8 update 66.  Updated one workstation to the latest version anyways just as a test, made sure only 32 bit version of Java was installed

      2. Removed Anti Virus from both the hosting server and a workstation.

      3. Made sure port 5003 was reserved on the server for only so no other process was taking it.

      4. Disabled backup the %programfiles%\FileMaker directory

      5. Disabled Shadow Copies

      6. Disabled IP6 on NIC

       

      If we look in error logs on workstations after they experience the problem I will see the following error:

      Log Name:      Application

      Source:        Application Error

      Date:          03/31/2016 12:22:03 PM

      Event ID:      1000

      Task Category: (100)

      Level:         Error

      Keywords:      Classic

      User:          N/A

      Computer:      %computername%

      Description:

      Faulting application name: FileMaker Pro.exe, version: 13.0.1.194, time stamp: 0x526aac3b

      Faulting module name: ntdll.dll, version: 6.1.7601.19160, time stamp: 0x56bcd51f

      Exception code: 0xc0000005

      Fault offset: 0x00067a51

      Faulting process id: 0x14d8

      Faulting application start time: 0x01d18b479a32eb0d

      Faulting application path: C:\Program Files (x86)\FileMaker\FileMaker Pro 13\FileMaker Pro.exe

      Faulting module path: C:\Windows\SysWOW64\ntdll.dll

      Report Id: b33dc0e2-f75c-11e5-9c35-7c5cf89e6b1d

      Event Xml:

      <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

        <System>

          <Provider Name="Application Error" />

          <EventID Qualifiers="0">1000</EventID>

          <Level>2</Level>

          <Task>100</Task>

          <Keywords>0x80000000000000</Keywords>

          <TimeCreated SystemTime="2016-03-31T16:22:03.000000000Z" />

          <EventRecordID>2917</EventRecordID>

          <Channel>Application</Channel>

          <Computer>%computername%</Computer>

          <Security />

        </System>

        <EventData>

          <Data>FileMaker Pro.exe</Data>

          <Data>13.0.1.194</Data>

          <Data>526aac3b</Data>

          <Data>ntdll.dll</Data>

          <Data>6.1.7601.19160</Data>

          <Data>56bcd51f</Data>

          <Data>c0000005</Data>

          <Data>00067a51</Data>

          <Data>14d8</Data>

          <Data>01d18b479a32eb0d</Data>

          <Data>C:\Program Files (x86)\FileMaker\FileMaker Pro 13\FileMaker Pro.exe</Data>

          <Data>C:\Windows\SysWOW64\ntdll.dll</Data>

          <Data>b33dc0e2-f75c-11e5-9c35-7c5cf89e6b1d</Data>

        </EventData>

      </Event>

       

      I also see he same error and the only variance is the 'Faulting Module Name'.  The other entries here could be:

      Faulting Module Name: FileMaker Pro.exe, version: 13.0.1.194

      Faulting Module Name: unknown, version: 0.0.0.0

      Faulting Module Name: FMEngine.dll, version: 13.0.1.54899

      Faulting module name: PROOFREADER.dll, version: 13.0.1.0

       

       

      I have found the following message on only one machine so far:

      Log Name:      Application

      Source:        Application Hang

      Date:          04/06/2016 11:06:43 AM

      Event ID:      1002

      Task Category: (101)

      Level:         Error

      Keywords:      Classic

      User:          N/A

      Computer:      NEG-WS024.int.newerasite.com

      Description:

      The program FileMaker Pro.exe version 13.0.1.194 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.

      Process ID: 1698

      Start Time: 01d190125a19bd1c

      Termination Time: 31

      Application Path: C:\Program Files (x86)\FileMaker\FileMaker Pro 13\FileMaker Pro.exe

      Report Id: 283c4edd-fc09-11e5-b3e3-acfdce970ea9

       

       

      Event Xml:

      <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

        <System>

          <Provider Name="Application Hang" />

          <EventID Qualifiers="0">1002</EventID>

          <Level>2</Level>

          <Task>101</Task>

          <Keywords>0x80000000000000</Keywords>

          <TimeCreated SystemTime="2016-04-06T15:06:43.000000000Z" />

          <EventRecordID>2458</EventRecordID>

          <Channel>Application</Channel>

          <Computer>%computername%</Computer>

          <Security />

        </System>

        <EventData>

          <Data>FileMaker Pro.exe</Data>

          <Data>13.0.1.194</Data>

          <Data>1698</Data>

          <Data>01d190125a19bd1c</Data>

          <Data>31</Data>

          <Data>C:\Program Files (x86)\FileMaker\FileMaker Pro 13\FileMaker Pro.exe</Data>

          <Data>283c4edd-fc09-11e5-b3e3-acfdce970ea9</Data>

          <Binary>55006E006B006E006F0077006E0000000000</Binary>

        </EventData>

      </Event>

       

      A few seconds after this happens on a workstation, FileMaker server will record this message on the 'Status' screen:

      Client " %Client Name% %computername% %ipaddress%" no longer responding; connection closed. (10)

       

      Any help or insight on this would be greatly appreciated