There is an error on this page....

I keep getting this error in various pdf files created from Word. The files are created in a workflow that has several people making changes to the files. We change header and footer information, change logos, make the file print ready (rgb to cmyk, text to 100%K, etc). Files get emailed (if small enough) and uploaded to Sharepoint and Dropbox for distribution.
How do we troubleshoot this error message and repair whatever is wrong? Some people find that once the message appears on a page, it doesn't appear in the rest of the document but if the same file is opened to the following page, the message comes back on that page and so on all the way through the document. I have not had that happen myself but I have opened the same file and not found any of these messages.
What would cause this erratic behavior?
The printer rejected the file because of errors converting to postscript to print the document. Could these be different problems?

Both of these suggest file corruption. Common with emailing. Don't email PDFs, ever.

Similar Messages

There was an error processing a page. there was a problem reading this document (110)?

hi
my name is kapil and i am trying to open one (which is downloded) pdf document.which giving me an error as there was an error processing a page. there was a problem reading this document (110) for some page only. i am using acrobat reader x. is it any 3d setting or any thing else please give me an idea. i am waiting for replay as soon as possible...........
your sincerely
KAPIL TRIVEDI

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.

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

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.

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.

Error message "There was an error processing the page.there was a problem reading this document(109)

Getting an error message when viewing the pdf report by using Adobe reader "There was an error processing the page.there was a problem reading this document(109)"

Hi,
We are using Active reports tool to generate the PDF document, And the
server is Windows 2003, and it is online document which generates
dynamically
We are facing the below error message when we try to generate, and my
local machine having Adobe Reader 7.0
Please find the screen shot below for the error message, Thank you for you
help in advance.
Thanks and Regards
Inayath Nalgar

"There was an error processing a page. Out of memory." Adobe Acrobat 9 Pro-Please Help!

"There was an error processing a page. Out of memory." Adobe Acrobat 9 Pro I had this problem with my last computer over two years ago which was obviously an older version of windows and acrobat and had found a way to solve it but like I said it was an older version and was 2 years ago so I don’t remember how to fix it. I’ve looked through many forums and emptied my temp folder I’ve uninstalled and reinstalled the software I’ve turned off my anti-virus I don't have adobe reader because I know this causes comflicts also and have tried so much more and I’m still having issues with about half my pdf files I cannot figure it out. I use pdf files many times a day and this is really hindering my work so please please please if anyone else has experienced this or knows how to fix it that would be great thank you!!! I’m somewhat computer savvy but not completely so if you cloud please explain to me in slightly less tech terms that would be great too.

Assuming your disk is not too full, and your virtual memory settings are normal, this is not caused by software clashes, TEMP folders nor fixed by reinstalls. It is Acrobat _actually_ running out of memory, or running out of something else it has a fixed supply of.
1. Are you using any plug-ins to process files?
2. After you get this error on a particular file, restart Acrobat. Does the file now open OK?

Error Message: "There was an error processing a page. A file I/O error has occurred"

Hi
I am running Windows XP on a lab top for a while. Just recently, every time I opened PDF files, I was getting an empty page. So, I installed the latest Adobe Reader. After that I started getting the error message "There was an error processing a page. A file I/O error has occurred".
Does anybody have a solution to this?
Thanks in advance.

I found my problem. My down scale quits, but quits as in not showing it's working. (I was confused too). Most all files can not be seen until fully downloaded. For whatever reason, perhaps a glitch or the new modum or video card. When downloading do not interupt as in wanting to view a page, but go to Network and Sharing Center (bottom right hand corner - click the computer running symbol) and click View Status. See Activity. If the numbers are rolling you are recieving. Waiting until it is complete. This is madding, but I've learned to live with it.
Hopes this helps.....

There was an error processing a page. a number is out of range.

When I open a PDF generated from a classic ASP application, some particular documents fail when accessing a page: there was an error processing a page. a number is out of range.
This only happens in Adobe Reader 10 and 11.
The ASP page has a code similar to this:
Response.AddHeader "Content-disposition", "attachment; filename = doc.pdf"
Response.ContentType = "application / pdf"
Response.Write Session ("PDF")
Try adding different settings in the properties AddHeader / ContentType / CharSet etc, but always the same.
In the screenshot you can see the mistake in page 3
Any idea?
thank you very much

Sounds like the pdf is corrupt. Try a forced quit. (command option escape)

SSRS PDF Export. There was an error opening this document. This file is damaged and could not be repaired

Hello,
I just experienced this problem, and was able to successfully mitigate. I wanted to share my experience and Solution.
The problem started with the following error after succesfully exporting a PDF Document. "There was an error opening this document. This file is damaged and could not be repaired."
This is only applicable if you can still export and open SSRS Reports to other formats. Go to the Log files of the SQL Instance. In my particular case I used the Default MSSQL instance: C:\ Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting
Services\LogFiles
The Folder will begin with MSRS (SRS is for SQL Reporting Services)
Sort the files by date modified and check for the most recent log file: ex. SQLDmpr0000.log The 0000 will be the incremental amount of errors you have experienced in SRS. Check for the following error:
"System.DllNotFoundException: Unable to load DLL 'T2Embed': Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))"
Below is a sample from the log.
reportrendering!ReportServer_0-1!1b78!02/07/2012-11:56:03:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.UnhandledReportRenderingException: , Microsoft.ReportingServices.ReportProcessing.UnhandledReportRenderingException:
An error occurred during rendering of the report. ---> Microsoft.ReportingServices.OnDemandReportRendering.ReportRenderingException: An error occurred during rendering of the report. ---> System.DllNotFoundException: Unable to load DLL 'T2Embed': Access
is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
   at Microsoft.ReportingServices.Rendering.ImageRenderer.FontPackage.TTGetEmbeddingType(Win32DCSafeHandle hdc, UInt32& status)
   at Microsoft.ReportingServices.Rendering.ImageRenderer.FontPackage.CheckEmbeddingRights(Win32DCSafeHandle hdc)
   at Microsoft.ReportingServices.Rendering.ImageRenderer.PDFWriter.ProcessFontForFontEmbedding(PDFFont pdfFont, Dictionary`2 embeddedFonts)
   at Microsoft.ReportingServices.Rendering.ImageRenderer.PDFWriter.EndReport()
   at Microsoft.ReportingServices.Rendering.ImageRenderer.PDFRenderer.Render(Report report, NameValueCollection deviceInfo, Hashtable renderProperties, CreateAndRegisterStream
createAndRegisterStream)
   at Microsoft.ReportingServices.Rendering.ImageRenderer.RendererBase.Render(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo,
NameValueCollection clientCapabilities, Hashtable& renderProperties, CreateAndRegisterStream createAndRegisterStream)
   --- End of inner exception stack trace ---
   at Microsoft.ReportingServices.Rendering.ImageRenderer.RendererBase.Render(Report report, NameValueCollection reportServerParameters, NameValueCollection deviceInfo,
NameValueCollection clientCapabilities, Hashtable& renderProperties, CreateAndRegisterStream createAndRegisterStream)
   at Microsoft.ReportingServices.ReportProcessing.ReportProcessing.RenderFromOdpSnapshot(IRenderingExtension newRenderer, String streamName, ProcessingContext
pc, RenderingContext rc)
   --- End of inner exception stack trace ---;
If you notice the error states that T2Embed.dll access is denied. In my case this due to a hotfix installed by Microsoft:
MS11-087: Vulnerability in Windows kernel-mode drivers could allow remote code execution: December 13, 2011
Be advised, in order to fix your problem and render pdf's, a vulnerability shall be created.
To fix this issue and allow the export to PDF work correctly, you must give the system Read/Execute Permissions, and Built-in\Administrators Full Control.
Go to Windows\System32 and find the T2Embed.dll Go to Security and modify the permissions as listed above. Do the same to the T2Embed.dll in the SysWow64 folder.
Restart Reporting Services and you will be able to export to PDF.
Best Wishes!
Mariano
www.lucontech.com

I'm not convinced this is the exact cause of the issue. I will check my log files to see if I find anything like what you described. However, I get this error when a particular user tries to do a "print preview" from a custom button. The
code builds a ReportViewer object, sets the ReportPath, etc.
The reason I'm not convinced is because we have a separate reports page that has the report viewer embedded into it. If the user generates the report that way and exports to PDF, Word, etc...the user can generate the file and be on their way. As
soon as the user clicks our "Print" button on the page without the ReportViewer embedded, the above mentioned error occurs.
UPDATE: Perhaps we have a different problem since my issue is from a custom button. I found the solution
here and confirmed the solution with the customer. It had to do with the code using Response.Flush() instead of Response.End().
One thing I noticed before I implemented the change: When you would close the PDF, it would ask you to save changes to the PDF. After implementing Response.End() instead, that prompt went away. No doubt it has to do with the differences between
how Response.Flush() and Response.End() handle the stream returned.
Anyway, posting in case someone has the same issue.

Pro 9 Users Receive "There was an error opening this document. The file is damaged and could not be repaired."

Users with Adobe Acrobat 9 Pro (Windows XP) are not able to open PDFs created on the server. They receive the error message:
“There was an error opening this document. The file is damaged and could not be repaired.”
Even if the users save to disk and try to re-open, the error still occurs.
This error did not surface in our QA testing because we were testing with Adobe Acrobat Reader 8. What can the difference be? Is there additional information that I can look for in order to troubleshoot this?
Thank you for looking at my post. Please provide guidance in trying to resolve this issue.
Elsa

So, I'm not sure how much this will help but if you save the pdf AHW_Test_05112009xx.pdf and open it in a text editor, and go all the way down to the bottom where the %%EOF marker is, it looks as if the html page is getting appended to the end of the pdf. I recieved the "This file was damaged..." error in Adobe 7.1.0 when trying to open it but if you remove the html at the end, it opens up just fine.
It appears that whatever's appending the html to the end is causing the issue.
Below is what the file looks like near the end after the EOF:
startxref
400771
%%EOF
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head><title>
Gartner for IT Executives
</title>

Exporting PDF files from SSRS 2012 - "There was an error opening this document. The file is damaged and could not be repaired"

Good day
I have the situation where we are exporting PDF files from reporting services in our website.
When dividing the data into sections, the report exports perfectly, but when exporting the entire set and trying to open the file, we get the following error in Adobe Reader:
"There was an error opening this document. The file is damaged and could not be repaired"
We tried to repair the file, no luck. We tried to use different PDF readers, no luck
We then checked the file sizes. When exporting the subsections, each section exports a file of about 2mb.
When exporting the entire set, the file is about 1.3mb.
Adding all the sections together gives me a rough estimate of 40mb.
Exporting to TIFF works beautifully and returns a file of 41.5mb. Word and Excel formats also work well, only issue there is the page numbering and formatting.
The problem we have is the clients are adamant about having it in PDF format.
Any advice please?

This was one of the temporary suggestions I gave the client...
Unfortunately they do not like this as the page numbering and formatting in Word does not appear right. We are talking about over 1300 pages. I can't expect them to change the formatting with each export. Additionally, the data is
constantly changing and each client has their own data. The clients export the reports randomly. I therefore can't post the reports back onto the server.
Thanks for the speedy response though

Adobe Photoshop Elements 9.0.3 Update There was an error downloading this update. Please quit and try again later. Photoshop Camera Raw 6.5 Update There was an error downloading this update. Please quit and try again later.

Adobe Photoshop Elements 9.0.3 Update
There was an error downloading this update. Please quit and try again later.
Photoshop Camera Raw 6.5 Update
There was an error downloading this update. Please quit and try again later.

Hi,
Which operating system are you running on?
For PSE 9, the update process was best using a manual method.
Are you trying to do Help - Updates?
If so try these downloads (fand follow the manual instructions given on the pages.
Adobe - Photoshop Elements : For Windows : Adobe Photoshop Elements 9.0.3 update
Adobe - Photoshop Elements : For Windows : Camera Raw 6.5 update for Elements 9
Adobe - Photoshop Elements : For Macintosh : Adobe Photoshop Elements 9.0.3 update
Adobe - Photoshop Elements : For Macintosh : Camera Raw 6.5 update for Elements 9
If you are getting an error during the download please try a different browser.
Brian

There was an error attaching this file

I wanted to send an email and I tried to attach a file from pages, I have tried several times but I always get
"there was an error attaching this file"

Is the file open in Pages when you're trying to attach it? Save and close it first.

Adobe CS5 Updates fails !!! There was an error downloading this update HELP

Adobe CS5 Updates fails !!! There was an error downloading this update HELP (Windows)

I have the same problem, but I'm on a mac 10.9. I have 2 folders inside the Adobe Patch folder inside the Adobe folder. The items have a bunch of letters and numbers.
I've attempted 2 downloads, each going through almost the whole process and stopping about 90% saying unable to install, fix the problems listed below (there was an error downloading this update, please quit and try again later). When I click on the consumer support for further assistance, it takes me to an Adobe page that says “This serial number is not for a qualifying product. Please try another” . I have CS4 design premium, CS5 design standard, and Acrobat Professional installed.
Thanks

There was an error installing this update. Please quit and try again later. Error Code: U44M1P34

This issue I got when I update InDesing CC.
There was an error installing this update. Please quit and try again later. Error Code: U44M1P34

I got this error trying to download and install updates to Photoshop Elements. In my case the message said that two updates could not be downloaded.
Of course, the idiot installer had installed Adobe Premier Elements trial over my dead body, and in navigating here I caught references on pages to installation of Reader, which I do not want, what with it's being incredibly vulnerable and inferior to any number of PDF readers out there.

When I attempt to open a PDF file I saved from a website, I get the message "There was an error opening this document. The file is damaged and could not be repaired." Is there any way to correct this problem?

When I attempt to open a PDF file I saved from a website using Safari, I get the message "There was an error opening this document. The file is damaged and could not be repaired." When I save the same PDF file using FireFox it opens up immediately. Is there any way to correct this problem with Safari?

Back up all data.
Triple-click the line of text below to select it, the copy the selected text to the Clipboard (command-C):
/Library/Internet Plug-ins
In the Finder, select
Go ▹ Go to Folder
from the menu bar, or press the key combination shift-command-G. Paste into the text box that opens (command-V), then press return.
From the folder that opens, remove any items that have the letters “PDF” in the name. You may be prompted for your login password. Then quit and relaunch Safari, and test.
The "Silverlight" web plugin distributed by Microsoft can also interfere with PDF display in Safari, so you may need to remove it as well, if it's present.
If you still have the issue, repeat with this line:
~/Library/Internet Plug-ins
If you don’t like the results of this procedure, restore the items from the backup you made before you started. Relaunch Safari again.

There is an error on this page....

Similar Messages

Maybe you are looking for