1 Reply Latest reply on Oct 26, 2012 11:29 AM by philmodjunk

    Closing Unexpectedly

    josebetzy

      Summary

      Closing Unexpectedly

      Product

      FileMaker Pro

      Version

      12

      Operating system version

      Windows XP Pro

      Description of the issue

      For some reason while the client is working it just closes. At times it would say that windows had to close due to a problem. Some times it just closes without saying anything. We have run virus checks, malware trojan checks, etc and all reports clean.

      This started when we moved over to 12 from 11. We have installed the recent 12.03 and the Advanced Server is up to date. Yet it continues on some PC's but not all. It does not happen on Windows 7 machines only on the XP and they are all up to date.

      Now this is the only customer that it is happening becuase the others do not report this problem and they are on Pro 12 up to date also.

      Any ideas let us know. Thank you.

      Steps to reproduce the problem

      Unable to reproduce

      Expected result

      Unable to determine

      Actual result

      Unable to determine

        • 1. Re: Closing Unexpectedly
          philmodjunk

               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:

               msconfig

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