1 Reply Latest reply on Jan 21, 2013 10:19 AM by disabled_ntaylor

    Filemaker crashing when I try to create a pdf



      Filemaker crashing when I try to create a pdf


      FileMaker Pro



      Operating system version

      Windows XP

      Description of the issue

      When I am trying to create a pdf file instead of printing several records (and this usually occurs when I'm printing in list view), the Adobe pdf symbol and the window appear, but then FileMaker and Adobe go into "not responding" mode.

      My printer drivers are up to date. I have an HP Officejet 6500A Plus. I've checked my layouts, and they seem to be OK (pages should print). Sometimes after the crash, when FileMaker re-opens, the pdf request will finish/appear, either as a partial print or a full print.

      But, this is very frustrating because I convinced everyone at this office to switch to FileMaker Pro from MS Access, and now this is happening. I hope that there is a bug fix soon!!

      Steps to reproduce the problem

      Open database, do a find for certain records, switch to new layout (viewed as list), ask to print,choose Adobe PDF from the menu.  I've also tried switching to Preview mode and using the "Save as PDF" option. Same result.

      Expected result

      I need the records to print to PDF.

      Actual result

      The program crashes and does not print to PDF.

      Exact text of any error message(s) that appear

      Happened again this morning. Text said: 

      %%[ ProductName: Distiller ]%%
      %%[ Error: ioerror; OffendingCommand: imageDistiller ]%%


      %%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
      %%[ Warning: PostScript error. No PDF file produced. ] %%

        • 1. Re: Filemaker crashing when I try to create a pdf

               Terry Mingle:

               Thank you for the post.


               To attempt to replicate this, on my computer running Windows XP Service Pack 3, I created a new database file called TestPDF.fmp12. I added a single field and added 5 new records. 


               My program does not crash either from a scripted PDF creation in Windows XP with Adobe or by using the "Save as PDF" option in Preview on Mac OS X.


               Are you able to replicate this in a new database file?


               If not, running recovery on your file may be a good idea to see if any problems are reported. Even if no problems are found, I'd test the recovered copy to see if it still exhibits the same behavior.


               Things to keep in mind about Recover:


               While Recover almost always detects and fully corrects any problems with your file...


               1. The recovered copy may behave differently even if recover reports "no problems found".

               2. Recover does not detect all problems

               3. Recover doesn't always fix all problems correctly

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


          What to do when your file is corrupt (KB5421).


               If you are able to replicate this behavior outside of the current database file, using a new database file built in FileMaker Pro 12 or one of the starter solutions, please let me know.



               FileMaker, Inc.