We had a client with similar problem a few weeks ago.
Solution was to use DynaPDF with MBS Plugin to optimize PDF which also repairs errors in the PDF.
I don't use any plugins and would prefer not to. The issue has only just developed. The only relevant change since last successful run (4/7/16) has been upgrading to Adobe Acrobat Pro DC on 6/7/16. I'm wondering if that has anything to do with this.
there are issue reports about this issue
- happens with classic theme
- could be a font-issue as well
Here, we change the theme from classic to something 'printable', after this, we could save fine pdfs. It happened when adding pdf's, 'normal' pdf's were fine IMHO
Might be the same with FileMaker 14.06 (changement of the pdf-engine, same as under V15)
Strange thing is, that it went fine until 'date'... therefore, I'm not quite sure if it's the same issue...
Changed Adobe files are extremely likely to be at issue, based on some of Acrobat's previous updates in years past. Can you roll back Acrobat and disable Adobe auto update?
I'm going to try that if I have to. The only thing that makes me focus more on the generation of the pdf is that Preview can't open them either.
Well, I'm really none the wiser, but today the problem has gone away. My first test was to open the file in FMA14—no problem. Then I opened it in FMA15 and expected a repeat of what was happening yesterday, but no—worked OK. Both of those tests were manual saves to the desktop, via the menu. Then I ran the full scripted routine on the two records that gave trouble yesterday and all is running normally. So I'm at a loss, but the issue has gone away.
Reminds me of the four engineers travelling together in a hire car when suddenly, for no apparent reason the engine died. Pulling off the road the chemical engineer, who was driving, said: "I think there's a problem with the fuel." The electrical engineer said: "I doubt it. More likely the alternator has failed." The mechanical engineer blamed the fuel pump. The computer engineer, however, said: "Well before we try anything else, let's all just get out, then get back in again and see if it starts."
Thanks Christian, Marcus and Stephen for your comments. I'll leave the discussion open for the moment in case it arises again.