Skip to main content
A
Anonymous
October 6, 2012
Question

Error message: There was an error processing a page. There was a problem reading this document (110)

  • October 6, 2012
  • 2 replies
  • 25871 views

I opened a pdf document in Adobe Reader X. When I attempted to scroll through the pages the following error message appeared, “There was an error processing a page. There was a problem reading the document (110). After an Internet search to try to find the reason for the error and a solution, I came across a site that suggested it was an issue regarding the fonts of the document. I then reopened the document and went into the document’s font properties (FILE – PROPERTIES – FONTS tab). There I noticed that the “Gathering font information” stopped at 2% which, of course, I took to mean that Adobe Reader X was having a difficult time in loading the font’s information. Another site suggested opening the document in the pdf reader, Foxit. So I did, and the document loaded properly with no error messages. I was still curious as to why the document did not load entirely in Adobe Reader X and if the same problem would occur using a different reader. I then downloaded the pdf reader, Nitro Reader 2. I opened the same document and initially received the following message, “The requested page number is invalid and does not exist in this document.” I closed the message and proceeded to scroll through the document. As I scrolled, the following message appeared, “This file was damaged (corrupted) and has been repaired.” I thought, “Wonderful!” I then chose <FILE – SAVE AS – PDF DOCUMENT> and saved the “repaired” document under a new name. When I opened the “repaired” document with Adobe Reader X, behold, the document opened entirely with no error message. I was curious, so I went into the document’s font properties and noticed, this time around, that the “Gathering font information” loaded to 100%. Nitro Reader 2 detected the error and fixed it. Now I’m left to wonder…why wasn’t Adobe Reader X able to do the same? I hope this post helps others who are experiencing the same issue.

    This topic has been closed for replies.

    2 replies

    morlaine
    morlaine
    Participant
    January 12, 2016

    I had a number of files that Adobe could not read.  Only the number code was 111 instead of 110.  I tried opening them with Nitro PDF and they opened like a charm.  I immediately changed my default reader to Nitro.  No muss, no fuss, and Nitro is FREE.  I don't do much with PDF files but I understand that Nitro will also write PDF files.  Suits my needs.

    MichaelKazlow
    MichaelKazlow
    Legend
    October 6, 2012

    When an pdf document is corrupt, there can be many reasons for that. It is not always clear how to handle corruption. Some hackers try to craft corrupt pdf files that will cause Reader to crash or have your computer run executable files that can infect your computer. Adobe as one of the makers of large and widely used software is often a target of hackers. The easiest thing to do is to refuse to open pdf files that do not properly conform to the standard. How many hackers are going to try to target Foxit's handling of corrupt pdf files?

    zopfan
    zopfan
    Known Participant
    March 31, 2014

    When I encountered an error "there was a problem reading this document 110" in Acrobat Pro 11 on 28.7 MB CS6 file, it indeed was very frustrating.

    I solved my problem, but since I don't know which step benefitted me, I've to enumerate all the steps I took:

    Read below:

    1.1. I could copy the file anywhere on the drive, but couldn't 'save as' from Acrobat Pro.

    1.2. No document security was applied of any sort on the file.

    1.3. Still in the first tab of the document properties, all details under advance section were empty. No 'PDF Version' 'location' 'file size' etc were populated. Nothing.

    1.4. I couldn't change and save anything in any of property dialogue. I could comment on the text, but as soon as I tried to save, it gave an error (some sort of 'File reading' error).

    1.5. When I tried to extract a page (I tried many), it gave 'reading error'.

    1.6. I didn't try 'splitting error'. Since I was 100% sure, it'll give me same reading error.

    1.7. I opened the file in Firefox and tried saving it as pdf from there. But no error, but no save either.

    1.8. I ran 'Remove Hidden Information' from protection panel without any errors.

    1.9. I tried 'sanitize document' from the same tab, but didn't succeed.

    1.10. Then (here I think the problem was resolved), from Document Processing panel, I did some commands. 1st, 'Export all images', successfully. Then 'Remove all links', it found 0.

    1.11. Then in 'print production' panel, I clicked/tried to open acrobat distiller. The same opened, did some processing. But I don't know if it did something in solving the problem or not.

    1.12. Although I think my problem was resolved till now, but the last step I did was 'Saved As' the file (from the file menu) as a .ps file. Though I've not yet reopened/used that ps file (to convert it into a pdf file again). But around here I wanted to close the file and it asked me whether I wanted to save the file, I said yes. And it saved the file correctly. And I checked that in properties dialogue, the missing information was populated too.

    1.13. Sorry for so lengthy instructions, but I had no choice.

    w11nga
    w11nga
    Participant
    October 21, 2015

    I had the same issue (error -110) and ran "Remove Hidden Information" from the Examine Document panel. It errored removing metadata but removed bookmarks, etc. Acrobat 9 crashed after saving the document but the file saved successfully and I was able to reopen the document and reduce the file size (my original goal). Removing hidden information worked for me.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices