Is the disk failing?
I see this all too often. While not exactly like your report, very very similar. Quitting and restarting FMPA *always* corrects the issue. It doesn't recur as quickly as your report suggests - immediately - but it's not too long before it needs a Quit/Restart cycle. I've also had Go refuse to save a PDF (silently on the iPad) and then a kill of Go and it's fixed. Same system accessed from 2 different clients experiencing the same -- issue.
I'm anticipating (with no facts to support me!) a dot n release from FileMaker to the 13.x product line to cleanup some of these kind of things
At least knowing others are experiencing similar behavior is conforting(?)
Where do you save the PDF and how the path is set ?
We are having this issue on 'various' computers primarily FMPA 13 on Mac 10.x. But also on some PCs.
Print a PDF to temp directory. One works then need to restart fileMaker.
Print to desktop One or two works then need to restart filemaker.....
We document stuff by printing PDFs and putting them into SuperContainer and our workflow for the moment is hozed....
Tryed changing OS - nope ( we have machines that are problems with Lion, Mt Lion and Mavericks.
So you might try this fix. ( talk about mildly ugly )
1. Reformat the mac.
2. Load 10.9
a. do all updates
3. Reinstall FMP.
b. probably kill the acrobat reader files so webviewer uses preview
We had one box that was 10.7.5
Updated to 10.8 - nope
upgraded to 10.9 nope
reformat and reload. - fixed.
Brings back such unfond memories of techsupport telling you to reload the system for just about any problem ;-)
I created a test file that shows if this is your problem.
We also see this problem.
I claim this has NOT to do with the file path. We have had the same problem. It has been difficult to prove this bug, as it seems to work different on different computers.
There is another known bug for which there is a solution. I believe most people here already did this, which is why they fail to get this save-as-pdf-bug, but that's my theory.
Anyway, after deleting the Adobe PDF plug-ins under Library -> Internet support, this bug DISAPPEARS for all my team members.