Skip to main content
Participating Frequently
July 17, 2009
Question

Document could not be printed

  • July 17, 2009
  • 79 replies
  • 769802 views

Unable to print numerous different PDFs from a corporate website. Each file has similar header, images, length, appearance. Opening the files online I receive the message "Insufficient data for an image" but the images do appear after I scroll down a bit. They disappear if I scroll up again.  Try to print and this message appears " Document could not be printed". I have tried saving and reopening in Reader 9.1, also printing to file and printing as an image. Nothing works. I think the two issues are connected.  I have seen similar discussions on this and other forums but they seem to lead nowhere.  Can anyone help please?

    This topic has been closed for replies.

    79 replies

    Participant
    July 25, 2011

    I cannot believe that this thread lasted for 2 years without a solution:

    Three options:

    If you're using Windows 7 (and possibly a Canon printer) you need to open Adobe and select "Help" > then "Repair Adobe Reader Installation". Make sure you printers are connected when you carry out this process. Carry out this process each time your Adobe Reader updates.

    This should fix your woes.

    Alternatively, (does not work all the time) select "Help" > then click on "Check Updates" (if any).

    As a last resort, right click on your Adobe shortcut > select "Properties" > then "Compatibility" and specify your Windows/Mac version. Go back to "Help" and check updates.

    However, the first option should work if you're using Windows 7.

    July 26, 2011

    PDFGenius wrote:

    I cannot believe that this thread lasted for 2 years without a solution:

    Three options:

    If you're using Windows 7 (and possibly a Canon printer) you need to open Adobe and select "Help" > then "Repair Adobe Reader Installation". Make sure you printers are connected when you carry out this process. Carry out this process each time your Adobe Reader updates.

    This should fix your woes.

    Alternatively, (does not work all the time) select "Help" > then click on "Check Updates" (if any).

    As a last resort, right click on your Adobe shortcut > select "Properties" > then "Compatibility" and specify your Windows/Mac version. Go back to "Help" and check updates.

    However, the first option should work if you're using Windows 7.

    Thnak you very much, this was solving my problem! (The same as discussed below) !

    Costa

    Fahrradteile & Bike Parts

    Participant
    June 21, 2011

    These pdfs must be corrupt files. Try downloading from a different source if possible.

    Participating Frequently
    June 21, 2011

    Most of the problem experiences referenced in this thread are with files created on the afflicted computer using another Adobe product, such as InDesign or Illustrator. You can't download a corrupt file if you aren't downloading a file in the first place.

    Participant
    June 20, 2011

    In Adobe Reader 9 there is an option in the Help menu called "Repair Adobe Reader installation".

    I had the same issue and this fixed it.

    Tim Cunningham
    Participating Frequently
    March 17, 2011

    I had the exact same issue printing an Adobe PDF Form we had created using Acrobat X.  However it was only for this form, other PDF printed fine.

    Symptom when trying to print this PDF:

    "The document could not be printed."


    and then

    "There were no pages selected to print."

    Resolution:  As I said this is our own software and we created the PDF with Acrobat X. The developer was asked to make an ammendment to an existing PDF Form. He copied and pasted from Word on to the document.  Apparently this also copied some hidden characters with it,  the PDF looked fine in Reader and looked fine in his version of Acrobat X.  However when I opened the PDF in my copy of Acrobat, there were obvious "gobbledy gook" characters (techincal term there)  I had him delete the two blocks or text he had altered, copy the text from word to notepad and then paste the block of text into the PDF.  Now it generates fine.

    I know this doesn't directly help any of you who are using software that is using Adobe PDFs, however if you don't get the above symptoms on ALL pdf's, only on some, then the issue lies with the 3rd Party Software company.  You could possibly point them to the above resolutoin that worked for my company.

    Thanks,

    Tim Cunningham

    Adobe Community Champion

    Participating Frequently
    March 18, 2011

    Ok, Now my ire is up...As an end user, I hate when the end user

    is made into a football and punted between in this case Adobe and a "3rd Party Vendor."

    Sorry, that doesn't play with me. I created a document with Adobe and immediately after saving the document with

    Adobe which CREATED the document, I got the error. So to blame this on a 3rd party vendor, I say bull sh*

    t"

    Tim Cunningham
    Participating Frequently
    March 18, 2011

    You can say whatever you like, Dr Phil, it doesn't change the fact that I *AM* a 3rd party vendor and in the case I mentioned above, this issue *WAS* caused by me.  My company however cleans up it's own mess rather than passing the buck to Adobe.  Your case may be different, I was just sharing my experience and how I resolved the issue.

    Did you create the PDF in question with Acrobat X?

    Did you convert it from another document using the Adobe Print Driver?

    If you can share the  PDF with me I would be glad to take a look at it.

    Thanks,

    Tim Cunningham

    Adobe Community Champion

    Participant
    January 31, 2011

    I was having this problem. I downloaded a freeware pdf unlocker and used it and resolved my issue. http://dailyfreeware.net/2007/05/15/freeware-pdf-unlocker-v104-2/

    Inspiring
    January 27, 2011

    Well, this is not getting any easier. Adobe responded:

    Thank you for contacting Adobe Technical Support. My Name is Amit. This is in  regards to your query posted on the Adobe web support portal regarding an issue  with Adobe Acrobat.

    We regret to inform you that we would be unable to  suppoer your request as ArcGIS mapping software is not in the list of our  supported softwares. I would request you to please contact ArcGIS about the  problem <(>&<)> they might hwlp you.

    We regret the  inconvenience caused.

    I don't think they really regret the inconvenience. They didn't even investigate to determine if the file I sent them was caused by a problem with the ArcGIS PDF engine or with Acrobat.

    But I did make some progress in another workaround and some clues, though not sure how many people it might help.

    ArcGIS offers the option to Export to PDF and then converts the map layers to a PDF layered document. When I tell it to export multiple pages to a single file, I get the error on print discussed here. However, if I choose to print each page as a single file, I do not get the print error in Acrobat 10 nor do I get it when I highlight all the individual PDF files and choose "combine into one file" -- the newly combined file also prints fine.

    And, when I choose the same map set in ArcGIS and instead of using the Export function choose FILE ==> PRINT ==> PDF (instead of a printer), it again will print fine on opening in Acrobat Pro 10.

    When you open Properties in each set and look at Advanced: PDF Producer, you get different producers for each. I don't know what this means, but it seems to be relevant. The maps that don't print show the PDF Producer as Adobe PDF Library 9.0 -- this is apparently the engine within ArcGIS.

    When, within ArcGIS, I choose Print to individual files (which is ultimately error free and prints) there is nothing shown in the PDF Producer space.

    When, within ArcGIS, I choos Print ==> Adobe PDF (which is also error free and prints) it shows as Acrobat Distiller 10.0.0 (windows).

    So I guess it would be useful for people having this problem to find out what the PDF Producer is and whether there's a relationship there.

    Workarounds to try, then, are to print to PDF from the original software creating the PDF and see if that helps. Probably not too many programs have a specific Export to PDF such as ArcGIS does, but if so, export as individual files then recombine them as a single document.

    I was able to contact a programmer at ESRI (makers of ArcGIS) and she's going to explore the problem from their side further.

    George

    Participant
    January 26, 2011

    Nullifidian,First check the printer and then try ,otherwise you can either copy to a new file and try it or else you could have install latest version of adobe reader and try it.Still,if the problem rise,you can contact a Adobe professional,for a solution.

    Participating Frequently
    January 26, 2011

    Here is my latest workaround. Since I use Google for my email, I view the document in

    Google email. When I have the full page viewing, I right click on the page and print it as a picture. The pain in the A about it is, I have t

    o do this for each individual page. Wish Adobe would fix the issue. I even had the problem with a PDF I created from scratch in Adobe Professional.

    Inspiring
    January 26, 2011

    Well, I just opened a ticket with Adobe and sent them the file I've been having trouble with. Yet another workaround was, in Acrobat Pro, to "Print to PDF" (!!), then open that document and print. It worked. So the problem for my document is back to multi-layers which are eliminated in both Print as Image and Print to PDF. The same sounds true for the Google fix above.

    I had also changed the suspect fonts to Times New Roman, and that didn't fix it.

    More later.

    George

    Participant
    January 12, 2011

    Hi all,

    I too am having the same problem - on only one computer in my office of 20 or so computers.

    When I attempt to print a document, I get the now infamous error "Document could not be printed" error in reader. Can still print from any other program, but need to use Adobe Reader. I tried it on both versions 9 and now Adobe Reader X, with the same results.

    I am running XP Pro completely updated. I have attempted the following:

    1.) In the print option, click "advanced" then select to print as image. Still can't print

    2.) Save the document onto the computer, open and tried to print. Doesn't work.

    3.) Uninstall completely everything with Adobe on it, and reinstalled. Still no go.

    The computer prints through another PC that has the printer shared. This setup is the same throughout my office, with no problems for other computers.

    Any help would be much appreciated, and I will update if I find anything out.

    Thanks,

    Richard

    Participant
    January 12, 2011

    We had the same problem here ("The Document could not be printed" and "No pages selected to print").

    I could replicate the problem only when printing to the network printer.  Printing to my local printer worked fine, which pointed to an issue communicating with the print driver.

    Our solution (or workaround) is to use a different print driver.  This is a solution we've used for a variety of printing issues over the years.  We had the same issue with Toshiba printers before, and now with Xerox printers:  Simply add a second version of the printer out there, share it with a name like Generic_Driver or something.  This will point to the same physical network printer, but instead of using the default Postscript driver, go into the printer properties and change the driver to a generic driver like the HP LaserJet 4.  At least in our case, many if not most PDFs print just fine using the default print driver, but it's a heck of a lot easier to troubleshoot printing problems if you've got an alternate print driver ready to go.  The problem will very often come down to an incompatibility between the software and the PS driver.

    Participant
    December 31, 2010

    I removed Adobe and while reading through the posts downloaded and then reinstalled the latest reader, Adobe Reader X (http://get.adobe.com/reader/).

    I am using Windows 7. It is working fine now.