1 Reply Latest reply on Apr 3, 2012 11:47 AM by philmodjunk

    Help requested



      Help requested


      Does the attached screenshot mean anything to anyone? I have a client using a FM 11 Pro runtime application on a Mac. She's been having issues which I suspect have been user related. The Windows users have not had any problems.

      She recently sent me this screenshot when the application crashed.

      Can you tell if this is user/application/OS related? And what do I do about it?




        • 1. Re: Help requested

          It's not unheard of for problems with a file to cause crashes on one platform and not another. Even different releases of the database can make a difference. Here's my standard post for dealing with a database that crashes. Not all suggestions may apply to your situation.

          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.

          To check for possible problems on a specific computer, you may want to run a utility to check out the hard drive and also to check out the user accounts on that computer for possible problems.

          To rule out some other issues with your specific computer on Windows systems,

          Select Run from the start menu and type in:


          Then, under the Services tab, you can stop all non-Microsoft services. If this solves the issue, then you need to look at what services you stopped and see which is one is the culprit.

          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 copy 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...