Error 21 occuring after update to 11.0.10

We updated to Adobe Reader X1 version 11.0.10 last week. When we try to SAVE a PDF document to our desktop we get the following
message and the file cannot be saved:
This document could not be saved. There was a problem reading this document (21).

The older version 11.0.06 works fine.

How can I fix this? Is there a patch for this?


Sales Coordinator


9 Answers

This is an indication of a corrupt PDF file. When you hold down the Ctrl key while clicking on the OK button on that dialog, you will get a bit more information. I am fairly certain that you would have run into the same problem with this particular file with the older version of Reader.

Karl Heinz Kremer
PDF Acrobatics Without a Net
PDF Software Development, Training and More...
http://www.khkonsulting.com


Karl Heinz Kremer   

I also had this problem, how ever the PDF was not corrupted. I have since taken this update off of the approved list of updates on our update server. After I did that I reinstalled Acrobat and adjusted the settings so it would not download and install updates on it's own.


Sasha Monroe   

We, too, are having the same problem. Not with all PDF's, only PDF's created through the web portal of our document scanning system. We did not have this problem until 11.0.10 was released and I am taking that off of our computers. I hope there is a fix for this.

Our "workaround" is to Save As Other -- Reduced Size PDF. Then the PDF behaves normally and we can modify it.


ABBE MEYERS   

The fix is to fix the software that creates your PDF files. There is nothing in Acrobat that needs fixing, it's a corrupt PDF file. Different version of Acrobat are more or less tolerant when it comes to corrupt PDF files. The more functionality that is packed into the PDF file format, the less tolerant a PDF viewer can be: In the past, there may have been only one way to interpret a certain error in the PDF file, but because another feature was added in this area, there now may be two or more ways to interpret a certain problem, and that may be the reason why a newer version of Acrobat or Reader is no longer able to just ignore the problem and open the file.

Any time you see one of these problems associated with an error number, when you hold down the control key and click on the "OK" button on the error dialog, you get more information about the nature of the problem - this will be a bit more technical than "There was a problem".

Fix the problem where it is rooted, and not just try to fix symptoms by not upgrading to Acrobat or Reader XI. Especially when it's clear that it's just files form one specific source.

Karl Heinz Kremer
PDF Acrobatics Without a Net
PDF Software Development, Training and More...
http://www.khkonsulting.com


Karl Heinz Kremer   

"The fix is to fix the software that creates your PDF files. There is nothing in Acrobat that needs fixing, it's a corrupt PDF file"
If that is the case why is Adobe working on a fix?


Brian Dailey   

Is there any progress on this? It really isn't good enough to blame corrupt files, as these are files which worked fine in previous versions. They work fine with 11.0.10 on Apple Mac as well, the problem seems to be only with the Windows release.

I have problems with PDF files generated by the pdfAmigo form generating site, so I will post on their forum as well, but I really think that this problem is primarily Adobe's.


DAvid Carter   

If we do what was suggested, hold down the control key and click ok in the dialog box, it says "This direct object already has a container". Not particularly helpful.


DAvid Carter   

I have removed Reader and reinstalled up to version 11.0.8. The email button no longer works with Google mail but we can now save PDFs again.

If you are interested, you must installed 11.0.0 then install each upgrade to 11.0.8
http://www.adobe.com/support/download...


Brian Dailey   

As I said, the information you get when holding down the control key is a bit more technical, and does not make sense if you don't have a good background in the PDF file format. What is still true is that you are dealing with corrupt files. Just because it worked in the past does not mean that these files are not corrupt. With newer versions of Acrobat and Reader, Adobe is packing more information into these PDF files, and it is possible that something that used to be easy to fix (because there was only one way something that looked "weird" could be interpreted) is now impossible to fix because the assumptions in the older software are not true anymore. Or, they fixed a bug that - as a side effect - is now no longer accepting a certain type of corrupt file.

In my almost 20 years of working with the PDF technology, I've never seen Acrobat or Reader flag a file as corrupt that was not corrupt.

It's your choice if you want to believe this, but it is very unlikely that Adobe will change the way Acrobat or Reader works just to accept files from PDF generators that are not following the PDF standard. If you want a fix, talk to the people who's software is creating corrupt PDF files.


Karl Heinz Kremer   


Please specify a reason: