1 Reply Latest reply on Aug 21, 2015 2:24 PM by philmodjunk

    FileMaker Pro has stopped working  - Windows 7



      FileMaker Pro has stopped working  - Windows 7


      FileMaker Pro



      Operating system version

      Windows 7 Professional - 64 bit

      Description of the issue

      I have a Windows 7 computer – it is about 5 years old.  I have always used Filemaker Pro without any problems.  Two weeks ago, I started received error messages doing random things such as clicking print, etc.  Now, it does not work at all and I cannot figure out the issue.  When I try to logon, I enter my info in log in screen and when I click enter, the message that is uploaded as a picture below comes up, saying “FileMaker Pro has stopped working – A problem caused the program to stop working correctly. Windows will close the program and notify you is a solution is available.”  I tried to repair the FileMaker Pro and even uninstall and reinstall it – and neither of those helped.  Please help me resolve this issue as I use this program daily for work.


        • 1. Re: FileMaker Pro has stopped working  - Windows 7

               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
          3.           Recover doesn't always fix all problems correctly
          5.           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...