1 Reply Latest reply on Jun 14, 2012 10:01 AM by philmodjunk

    Filemaker 12 Crashes when trying to run print script on converted database orig 5.5

    dcrossjm

      Summary

      Filemaker 12 Crashes when trying to run print script on converted database orig 5.5

      Product

      FileMaker Pro

      Version

      12.0 V 1

      Operating system version

      windows 7

      Description of the issue

      Trying to run print script

      Steps to reproduce the problem

      crashes sometimes and works sometimes

      Expected result

      Mostly crashes

      Actual result

      Filemaker crashes
      Problem signature:
        Problem Event Name:     APPCRASH
        Application Name:     FileMaker Pro Advanced.exe
        Application Version:     12.0.1.183
        Application Timestamp:     4f62a0d3
        Fault Module Name:     FileMaker Pro Advanced.exe
        Fault Module Version:     12.0.1.183
        Fault Module Timestamp:     4f62a0d3
        Exception Code:     c0000005
        Exception Offset:     00092d4d
        OS Version:     6.1.7601.2.1.0.256.48
        Locale ID:     1033
        Additional Information 1:     0a9e
        Additional Information 2:     0a9e372d3b4ad19135b953a78882e789
        Additional Information 3:     0a9e
        Additional Information 4:     0a9e372d3b4ad19135b953a78882e789

      Exact text of any error message(s) that appear

      Problem signature:
        Problem Event Name:     APPCRASH
        Application Name:     FileMaker Pro Advanced.exe
        Application Version:     12.0.1.183
        Application Timestamp:     4f62a0d3
        Fault Module Name:     FileMaker Pro Advanced.exe
        Fault Module Version:     12.0.1.183
        Fault Module Timestamp:     4f62a0d3
        Exception Code:     c0000005
        Exception Offset:     00092d4d
        OS Version:     6.1.7601.2.1.0.256.48
        Locale ID:     1033
        Additional Information 1:     0a9e
        Additional Information 2:     0a9e372d3b4ad19135b953a78882e789
        Additional Information 3:     0a9e
        Additional Information 4:     0a9e372d3b4ad19135b953a78882e789

      Workaround

      none
      new script reproduced from scratch crashes as well

        • 1. Re: Filemaker 12 Crashes when trying to run print script on converted database orig 5.5
          philmodjunk

          If you experience a crash when printing, it's helpful to identify the printer you are using and whether you have checked to be sure you are using the most up to date printer driver available. (You can usually check the printer MFG's web site for them.)

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

          In your case, since it happens when printing, it might be that your layout is corrupted and replacing the layout with a new one will resolve the issue.