What type of operating system are you running Acrobat 9 on?
Thanks for responding Lori, sorry to leave out some necessary info. We're running WIndows 7 Enterprise 64x. Running the 32x version of Adobe 9 STD,
One quick thing to check is if Windows Preview is being used in the windows open/save dialog.
Thanks for the suggestion Lori, unfortuantely this isn't the case. The issue appears preview agnostic.
1 person found this helpful
What tool is used to generate these PDF documents? You can check under File > Properties > Description tab. Also, in the same dialog, are there any unusual fonts?
Do you have the Pro. version of Acrobat around? Have you tried using Preflight to see if there are any syntax errors or font errors? It may be that the point update of Acrobat is more strick on determining the validity of the PDF and it's exposing something that a earlier version of Acrobat 9 did not. This can happen on PDF documents created using 3rd party tools, which are not necessarily formed properly.
Excellent suggestions Lori. We're unable to use Pro to troubleshoot at the moment, but we were able to see that all the files are generated by the same program under the description tab (GoSystems). I'm currently running through some test with my users to figure out how these documents are being saved.
We've narrowed the behavior to any deletion produces the Error (109) upon saving. This could be pages or even edits added during the same session. If any item is deleted, then saving the document will produce the error. Strangely enough, opening the document, doing save-as before any work is done, then overwriting the document with itself removes this behavior and the file behaves appropriately.
I'll let you know if any other problems crop up in Acrobat related to this issue, but for now it appears to be another companies template/print behavior + user issue.