Latex Error Pdf File Is Damaged
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions texworks save pdf you might have Meta Discuss the workings and policies of this
There Was An Error Opening This Document. The File Is Damaged And Could Not Be Repaired Pdf
site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or
\pdfminorversion=4
posting ads with us TeX - LaTeX Questions Tags Users Badges Unanswered Ask Question _ TeX - LaTeX Stack Exchange is a question and answer site for users
Texworks Pdf
of TeX, LaTeX, ConTeXt, and related typesetting systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top How to overcome Acrobat Reader error 131 with a pdfLaTeX doc? up vote 47 down vote repair damaged pdf favorite 15 I'm generating a PDF document with pdflatex (more precisely, latexmk invoked from TexMaker 3.4. My LaTeX install is TeXLive 20120719). I can read the document fine in Okular and Gmail's attachment preview, but a colleague that runs Acrobat Reader on Windows reports: "There was a problem reading this document (131)". EDIT: The error disappears when using \usepackage[demo]{graphicx}, which puts black boxes instead of the real images. They are all PDFs, PNGs and JPGs. Instead of using demo, I added the code for a \demoincludegraphics command, which makes the file work in Reader when using it to replace the logo in the headers, as shown below. But enabling it (using \includegraphics instead of \demoincludegraphics) and removing everything else also works in Reader! There is some strange global interaction that makes the file appear broken to Reader when enabling all the graphics... My code compiles fine, reason why I only attach the preamble and a simple text for a Minimal Working Example: \documentclass[12pt,lettersize,twoside]{article} \usepackage[utf8]{inputenc} \usepackage[spanish,es-tabla]{babel} \usepa
ElementsAdobe Dreamweaver Adobe MuseAdobe Animate CCAdobe Premiere ProAdobe After EffectsAdobe IllustratorAdobe InDesignView all communitiesExplore Menu beginsMeet the expertsLearn our productsConnect with your peersError: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page. Please enter a texworks tutorial title. You can not post a blank message. Please type your message and try again. latex to pdf More discussions in Acrobat Reader All CommunitiesAcrobat Reader This discussion is locked 15 Replies Latest reply on Jul 5, 2012 11:16 AM by failed to load pdf document zazougi The file is damaged and could not be repaired. (Robert_Lee_Anderson) Jul 7, 2008 9:18 AM Intermittently when we open a pdf in the browser in one of our main Enterprise applications, we get the error "The file http://tex.stackexchange.com/questions/64448/how-to-overcome-acrobat-reader-error-131-with-a-pdflatex-doc is damaged and could not be repaired." Downloading and opening always works (however for our system this is a less than acceptable workaround). The only common denominator we can find is that this is only happening in IE6 (no matter what version of adobe reader). IE7 always opens the pdfs fine, regardless of the reader version. I've seen this mentioned all of the place, and it often mentions that it's some sort of problem with the https://forums.adobe.com/thread/394450 pdf and that reader 8 handles it better. Any solutions yet? 134307Views Tags: none (add) This content has been marked as final. Show 15 replies 1. Re: The file is damaged and could not be repaired. MichaelKazlow Jul 7, 2008 9:01 PM (in response to (Robert_Lee_Anderson)) It sounds like MISE is not completely downloading the file, but IE7 is. Mike Like Show 0 Likes(0) Actions 2. Re: The file is damaged and could not be repaired. (Robert_Lee_Anderson) Jul 8, 2008 4:22 AM (in response to (Robert_Lee_Anderson)) Ok, any solutions to get IE6 to play nice? Like Show 0 Likes(0) Actions 3. Re: The file is damaged and could not be repaired. (Robert_Lee_Anderson) Jul 8, 2008 11:46 AM (in response to (Robert_Lee_Anderson)) We've just found that Adobe Reader 6 (not 7, 8, or 9) fixes this problem. Again, though, not an acceptable solution. Like Show 0 Likes(0) Actions 4. Re: The file is damaged and could not be repaired. (Robert_Lee_Anderson) Jul 8, 2008 11:48 AM (in response to (Robert_Lee_Anderson)) Also, loading the page with IE inside of Firefox with the "IE Tab" addon for Firefox works. Again, not acceptable! Like Show 0 Likes(0) Actions 5. Re: The file is damaged and could not be repaired. (Robert_Lee_Anderson) Jul 18, 2008 7:34 AM (in response to (Robert_Lee_Anderson)) Anyone have a solution? We also sometimes get: "Expected a dict object" Thi
the following workarounds Applies to : Acrobat X Acrobat XI Error: PDF document is https://helpx.adobe.com/acrobat/kb/pdf-error-1015-11001-update.html damaged and cannot be repaired Acrobat products have historically opened a PDF as long as the %PDF-header started anywhere within the first 1024 bytes of the file. http://tug.org/pipermail/pdftex/2012-November/008849.html No checks were performed on the extraneous bytes before the %PDF-header. However, the 10.1.5 and 11.0.01 updates improve security by enforcing stricter parsing of the PDF-header. file is The product now refuses to open the small fraction of PDFs that do not correctly start with the '%PDF-' header and an error appears: Error: the document is damaged and cannot be repaired. Adobe Reader could not open because it is either not a supported file type or because the file has been damaged file is damaged (for example, it was sent as an email attachment and wasn't correctly decoded). Solution: Use one of the following workarounds PDF creators If you manage or administer software that automatically generates PDFs, modify the way the PDF is produced. Make sure that no extraneous bytes appear before %PDF at the head of the file. PDF consumers: Enterprise admins and users If you are a customer or an enterprise IT professional, you can disable the header validation on machines by setting the appropriate preference. You can set this preference per user in HKCU or at the machine level for all users in HKLM. You can use a similar method on Mac OS by modifying the same plist preference. If the AVGeneral key does not exist, create it manually. The HKLM path is generically: HKLM\Software\Adobe\(product name)\(version)\AVGeneral\bValidateBytesBeforeHeader=dword:00000000 For example, to change the behavior for Acrobat 11.0, create a DWORD at this location: HKLM\SOFTWARE\Adobe\Adobe Acrobat\11.0\AVGeneral\bValidateBytesBeforeHeader=dword:00000000 The HKCU path is generically: HKCU\Software\Adobe\(product na
[ date ] [ thread ] [ subject ] [ author ] Here's the LaTex script: \documentclass{article} \begin{document} \SweaveOpts{concordance=TRUE} Hello \end{document} The error message from acrobat: 'There was an error opening this document. The file is damaged and could not be repaired.' I tried changing the pdf compiler used by Sweave from pfdLaTex to XeLaTex and this does generate pdf files that can be opened with acrobat. Best, Pieter Op 13-nov.-2012, om 22:35 heeft Paul Vojta