4 Replies Latest reply on Jan 5, 2012 10:54 AM by philmodjunk






      FileMaker Pro



      Operating system version

      Macintosh Snow Leopard and Lion

      Description of the issue

      Crashes. We are getting a lot of crashes on a Snow Leopard running older Mac Mini and a lesser number on a new Lion Mac Mini. Filemaker is used continuously through the work day. It just crashes. Reports are always sent to Apple. Filemaker may be getting these reports, but who knows.

      It is like there are still issues in compatibility with these newer operating systems.

      Steps to reproduce the problem

      Use of Filemaker continuously through the work day

      Expected result

      No crashes

      Actual result


      Exact text of any error message(s) that appear

      A message from the operating system that the Filemaker has crash and the details are being sent to Apple.

      Configuration information

      Snow Leopard running older Mac Mini and a lesser number on a new Lion Mac Mini.



        • 1. Re: Crashes

          Figuring out why FileMaker is crashing can require some sleuthing to rule out possible issues.

          Basic diagnostic tests to perform when you get frequent crashes or “Hangs”:

          Does the crash only occur with a specific file?
          Test by creating a small sample file and see if opening it and working with it also generates a crash. If it crashes too, the problem likely lies with the computer or it's installation of FileMaker. If it does not crash, it becomes more likely that there is a problem with the file.

          What is reported when you recover the file?
          The file could be damaged. Not only can file damage cause crashes, but the crashes (or forced quits after a "hang") can damage your file. You may need to test a recovered opy to see if it works without crashing.

          Things to keep in mind about Recover:

          1. Recover does not detect all problems
          2. Recover doesn't always fix all problems correctly
          3. Best Practice is to never put a recovered copy back into regular use or development. Instead, replace the damaged file with an undamaged back up copy if this is at all possible. You may have to save a clone of the back up copy and import all data from your recovered copy to get a working copy with the most up to date information possible.

          Does it always crash when you are doing the same thing with your file?
          That may point to a specific layout, script, operation that interacts with your Operating system or other applications...

          • 2. Re: Crashes

            Orlay Plummer,


            Thank you for your post.

            To assist you, some additional information would help.   The answers to PhilModjunk's post, and:

            Are both machines updated to the latest version of the Mac OS X and FileMaker Pro?  Since the message you are receiving is from the operating system, have you tried to open the file on the same machine under a different user?  Were the files that are now crashing ever working without any issues?



            FileMaker, Inc.

            • 3. Re: Crashes

              Before we got the new computers, we were using Filemaker 8.5 without crashing problems. With the purchase of some new Mac Mini's running Lion, we had to upgrade our Filemaker to version 11 and our capable older Mac Mini's to Snow Leopard. With these changes, the crashes of Filemaker began. One of the Lion mini's serves as the database server serving a mixture of clients on Lion Mini's, Snow Leopard Mini's and a Windows Vista machine. The program runs throughout the day, due data entry and searches varying depending on need. The files themselves started out as Filemaker 3 or 4 files (whatever the first version of Filemaker capable of relational databasing) and have been improved through time and converted to Filemaker 6 and Filemaker 7 formats.

              With Filemaker 11, we had to go to some of the scripts and essentially reconfirm some script steps (generally those dealing with bringing a layout in a file to focus or the foreground.

              The database server's Filemaker crashes occasionally, at seemingly random moments. The Snow Leopard machine's Filemaker crashes far more often. Upon restarting, no file undergoes any apparent recovery operation. Generally the last record being added is lost.

              • 4. Re: Crashes

                Note: File Corruption can be latent. That means it's present but nothing obviously wrong is happening to tell you that the file is damaged. In some such cases an upgrade to the database version or operating system (you've done both) will bring to light issues that were not apparent before the upgrade. That's one possible explanation. Perfroming the tests I suggested would help determine if this is the issue here or not.