3 Replies Latest reply on Jan 10, 2012 11:15 AM by TSGal

    Duplicate IPs / Client Lockout

    ToddWiener

      Summary

      Duplicate IPs / Client Lockout

      Product

      FileMaker Server

      Version

      11v2

      Operating system version

      OS X Server 10.6.7

      Description of the issue

      We have two database files accessed from FM Go up to 50 clients and up to 10 FM. This problem occurs, however, even if there are very few (as few as 5) active clients using FM Go. When executing a script that changes to a particular layout, all connected FM Go users become locked. If they exit and try to reconnect, a duplicate IP appears in the admin console, but the users cannot get further than a partial display of the initial layout, after which spinning occurs for these clients.

      The server continues to run scheduled backup scripts. But you cannot use the console to disconnect any clients, duplicates or otherwise. The way to restore the filemaker server is by restarting the host computer. Sometimes the host computer will not shut down normally and will have to be forced off with the power button.

      We have recreated the databases from earlier versions that did not seem to exhibit this problem, but then the problem returned.

      Steps to reproduce the problem

      We can sometimes reproduce the problem by tapping a button executes a script that switches to a layout. We have replaced both the script and the layout. The problem has still reoccured.

      Expected result

      Normal use.

      Actual result

      All connected FM Go clients freeze.
      Sometimes, connected FM Pro clients freeze.

      Exact text of any error message(s) that appear

      Spinning disc.

      Configuration information

      All iPads are running latest operating system and latest version if FM Go. Servers are running OS X Server 10.6.7. The servers are Mac Mini servers with 4 Gigs of ram and plenty of hard drive space. We have used a variety of hardware with the same results and have concluded this is not a hardware problem.

      Workaround

      Rebooting. We have started designing replacement software, but would prefer to continue using FileMaker, which I have been using for more than 25 years. Any ideas or advice would be appreciated.

        • 1. Re: Duplicate IPs / Client Lockout
          TSGal

          Todd Wiener:

          Thank you for your post.

          Obviously, something has changed with your computing environment since this used to work without incident.

          When you created a new Layout, did you use the "Duplicate Layout" command or did you create it from scratch?  If you used the "Duplicate Layout" command, any possible corruption with the layout would have also been duplicated.  Also, copying and pasting could be a problem.

          Are you using an Open Database script step to open the second database file?  Or, are you letting FileMaker Pro open the files automatically?

          A customer had a similar problem, and they discovered the log file to be 18GB.  Once that was removed, the problem disappeared.

          How large are the database files?

          Any other information you can provide may help me determine the possible causes.

          TSGal
          FileMaker, Inc.

          • 2. Re: Duplicate IPs / Client Lockout
            ToddWiener

            TSGal -

            We indentified a script that swithces to a particular layout as being the trigger for this bug. We have recreated the script and the layout but the probem has still occurred. I believe this was done for scratch, but will try agin.

            The second database file is opened automatically.

            Our database files are small. The data is flushed and reimpoted frequently. The file is 24 megabytes.

            Where is this log file that you are referring to?

            - Todd 

            • 3. Re: Duplicate IPs / Client Lockout
              TSGal

              Todd Wiener:

              I apologize for the late reply.

              The log files are found in the FileMaker Server -> Logs folder.  Check the size of each of those log files.

              TSGal
              FileMaker, Inc.