1 Reply Latest reply on Dec 12, 2014 5:16 AM by philmodjunk

    FMPro 3.0v4 crashes with every 2nd print attempt



      FMPro 3.0v4 crashes with every 2nd print attempt


      FMpro 3.0v4 running under MacOS 8.6. crashes every 2nd print attempt. Total crash of system, needs to be rebooted. It's a single user database, tested AppleTalk and Ethernet both same result. Printer is Postscript HP Laserjet 6MP. Printer driver version 8.6.5. Is this related to Filemaker or is it OS related? How may I debug this? The clientversion of Filemaker, does it write errorlogs somewhere?

        • 1. Re: FMPro 3.0v4 crashes with every 2nd print attempt

          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.

          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... In your case, you are getting a crash when you print. The interaction between FileMaker and the printer driver may be the issue. You can:

          a) check for an updated driver. (It's quite possible for FileMaker to "trip" a bug in the driver software that other programs--because they interact with the driver differently from FileMaker--do not and thus you can print just fine with other apps and not FileMaker. It's also possible that it's a FileMaker bug specific to certain printers.)

          b) try printing from a different file and from other layouts in the same file. Layouts can be corrupted and the issue not be detected by recover.

          c) try  saving as PDF and then printing the PDF

          d) try other printers/drivers

          e) if you can, try this with the same printer, but on a different computer