HELP! "This file is damaged and cannot be repaired."

I have been editing a large (25+ MB) PDF in Adobe Acrobat X Pro on a Macbook.
I just tried to open it to continue editing and got an error message:
"This file is damaged and cannot be repaired."
What on earth happened?!?!
A few days ago I saved a compressed version that is 1/10th the size. I can use that if I absolutely have to (it means losing part of my work and not all of my work) but I'm nervous -- what is the difference between a compressed file and a standard file that would make the compressed file 10% of the size? Is it fully functional with edits?
Ideally, if someone could help me remedy my error problem on the main file, that would be preferable -- but I'll also take info on compressed files (I didn't zip it, I just saved it in "Finder" as a compressed file.)

Lara,
yes it said something like "some fonts are not supported..etc...would you like to open the file anyway." (sry cant remember verbatim...I had a friend of mine try to open it on her comp which has cs3).
I believe CS3 should substitute the fonts in question, or at least give you the option to substitute them. Did you try saving it from CS3 (with or without font substitution) and then opening in CS4 as I suggested?
CS4 may be more particular than CS3 when it comes to fonts. Illy is more particular than most applications (some applications open files with corrupt fonts that she flatly refuses), and she may have become more particular over the years.

Similar Messages

"file is damaged and cannot be repaired" CS3 to CS4

hello,
I was emailed an illustrator CS3 file which I cannot open in CS4. I can open in CS3 but when I try to open in CS4 I get error "this file is damaged and cannot be repaired"
when I open in CS3 I get a message about font inconsistency...but the file still opens.
any suggestions?

Lara,
yes it said something like "some fonts are not supported..etc...would you like to open the file anyway." (sry cant remember verbatim...I had a friend of mine try to open it on her comp which has cs3).
I believe CS3 should substitute the fonts in question, or at least give you the option to substitute them. Did you try saving it from CS3 (with or without font substitution) and then opening in CS4 as I suggested?
CS4 may be more particular than CS3 when it comes to fonts. Illy is more particular than most applications (some applications open files with corrupt fonts that she flatly refuses), and she may have become more particular over the years.

Adobe PDF comes up and says "file is damaged and cannot be repaired" works fine in IE9.

Open a Adobe PDF on this site: http://www.safehaven.com/ and this specific PDF comes up with the "file is damaged and cannot be repaired: JAN30 EUR/USD Triggers Bearish Reversal Pattern into... - MIG Bank

there is something with the pdf itself that is stopping FF from opening it, as when i try opening the same in Crome ... there also i encounter the same problem (the file opens partially and then stops opening). But if i download the same then i can view the same in Acrobat reader properly.
May be the way the pdf was created used something which FF s not able to render (the graphics used in charts etc)
The work around that is available is that you download the file and save it somwhere, then open the same in Acrobat reader separately

PDF error message "The file is damaged and cannot be repaired"

Across several versions (upgrades) of Mozilla and from
several sites I have a problem when viewing pages (ie.
from MoinMoin wikis but also other CMS systems) with
embedded PDF documents.
I get an error dialog saying "The file is damaged and cannot be repaired" and a reference to a local cached copy of a
".tmp" file. If I right click on the link and "Save Link"
as a local file then the PDF views correctly (and it renders
correctly within the HTML page with other browsers such
as IE).
The page below (bizarrely) works for me, but similar
documents fail on password protected sites.
Any comments much appreciated. Thanks!
/Gareth Lee

Clear the cache and the cookies from sites that cause problems.
"Clear the Cache":
* Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now"
"Remove Cookies" from sites causing problems:
* Tools > Options > Privacy > Cookies: "Show Cookies"

File is damaged and cannot be repaired?

Whenever I try to open a needed file on my windows 7 pc, I get the above message. I need the file as soon as possible. Is there any way to repair the file so I can print off the document? I have heard of file repairers, but do they work?

Lara,
yes it said something like "some fonts are not supported..etc...would you like to open the file anyway." (sry cant remember verbatim...I had a friend of mine try to open it on her comp which has cs3).
I believe CS3 should substitute the fonts in question, or at least give you the option to substitute them. Did you try saving it from CS3 (with or without font substitution) and then opening in CS4 as I suggested?
CS4 may be more particular than CS3 when it comes to fonts. Illy is more particular than most applications (some applications open files with corrupt fonts that she flatly refuses), and she may have become more particular over the years.

Keep getting error:the file is damaged and cannot be repaired when i try to go into a web page

i am trying to go to a web page and keep getting an error

Clear the cache and the cookies from sites that cause problems.
"Clear the Cache":
* Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now"
"Remove Cookies" from sites causing problems:
* Tools > Options > Privacy > Cookies: "Show Cookies"

This adobe Muse site file is damaged and cannot be opened.

This is a nightmare. I finished this website, went to go and update and got the message that the site file is damaged and cannot be opened. Are you serious? What can be done to get the file back, and how can this be prevented from happening again? I may have to completely toss out Adobe Muse because this is not good. Please help.

Please send us the .muse file and the MuseLog.txt file from your Documents folder to [email protected] along with a link to this thread. If the files are larger than 20Mb you can use a service like Adobe SendNow, Dropbox, WeTransfer, etc. (If you use a service, please include your return e-mail address in the body of the message, since not all services include it in the sharing invite they send.) Thanks.
Was the file stored in a synchronized folder (i.e. Dropbox, Creative Cloud Files folder, etc.)?

This Adobe Muse site file is damaged and cannot be open.

Hi all,
While making some edits to my muse site, my mac froze, and I waited for about 10 mins and it was still frozen--so I forced restarted my computer. Upon re-opening the file, I received the message "This Adobe Muse site file is damaged and cannot be open." I was wondering if there is any way to recover the file. I have a very recent HTML export of the site, is there a way to re-import that into a muse file? Or perhaps the file is somehow able to recover? I'm on an iMac that was just bought. It's pretty frustrating because my last backup was from two weeks ago and there have been major updates to the design of the site. At the very least, I have the latest export to copy the layout from, but my site is 50+ pages. Thanks in advance for any help.
-Jack

I don't have good news. The file is truncated. It's shorter than it should be and the missing information isn't something I can manufacture.
From your description of events and looking at the information in your log file we believe you hit a rather obscure weakness in the Mac OS, or perhaps Mac hardware or the hard drives/controllers used. When an application writes to a file and requests the file be flushed to the physical media, two things occur. The first is the data is written to the physical media and the second is a table on contents on the media is updated to indicate the new length of the file. In this case it appears the Save completed successfully as far as Muse could tell (the success is reported in the log), but what probably occurred is either a very low-level OS crash and/or your restart of the computer occurred before the length of the file was updated in the table of contents.
Unfortunately, after some time spent searching online, it doesn't appear as though there are any Mac OSX tools that will re-extend a file without altering the bytes in the newly extended area. Or at least I couldn't find any (and it makes sense for security reasons that the old data wouldn't be there when the file was re-extended). Even if there is such a tool, it's very likely other activity on your machine since the restart has already overwritten those bytes with some other file, so the missing part of the file is now gone.
I'm sorry, but I'm not aware of any way to recover or repair your file.

Muse file is damaged and cannot be opened...Urgent support needd...loss of 40 hrs work

I had worked on Muse file for over 40 hrs...Now I cannot open the file.
It says the file is damaged and cannot be openned.
Urgent support needed!!!!!!!!!!!!!!!!!!

Jennifer, thank you for sending the two files. They've created more questions than answers.
Neither file shows any signs of the type of damage that occurs when a drive is removed without being ejected. I feel quite confident that's not the cause in this case.
Unfortunately the nature of the damage is such that to understand it I'm going to have to spend a significant amount of time developing some custom foreinsics tools. At least a few days of focused development. Unfortunately at the moment I have a few high priority deadlines looming along with an approaching vacation, so it's going to be at least a couple weeks before I'm going to make any progress on that.
Without the results of those foreinsics but from what I've seen in the file the most likely cause is one of two things:
1) Faulty hardware; or
2) A bug in Muse.
Neither of those is likely, but those are the two most likely causes I can theorize.
Faulty Hardware
From my experience on InDesign and now Muse I've come to realize hard drives fail far more frequently than most people realize. The fact that .muse (and InDesign) files are large means they cover more area on your hard drive and thus are more likely to be the first to encounter issues caused by a failing drive. The Muse file format is a database (as is InDesign's) that contains many many cross linked objects. If you save a large text file and one byte is scrambled the result is a misspelling in your text file and the word processor opens and displays the file fine. When one byte in a large image is scrambled odds are a single pixel will appear as the wrong color or transparency in your image editor. When a single byte in a database file is scrambled, it can break the interrelationship between objects and result in an unintelligible file to the application attempting to read it.
I recommend you run Disk Utility and any other hard drive verification software you might have to help rule out failing hardware.
A Bug In Muse
This is the one I'll lose sleep over until I find time to do the forensics, assuming the forensics turn up something fairly conclusive. If the cause is a bug in Muse, it's going to have to be something very obscure that for whatever reason is radically more likely to occur on your computer or with your specific usage pattern of Muse, since it's exceptionally rare for someone to reach this error and not have a file with obvious signs of hardware failure, drive removal without ejection, folder sync software issues or multiple users simultaneously editing a file on a server.

The muse file is damaged and cannot be opened

Help! I just completed my website for a company and was planning to publish it today but when i opened the file it states " the muse file is damaged and cannot be opened": What can i do now?

Nope, it is not synchronized to any online software. I merely made 2 copies, one in a hard disk, another in another computer. which cant be loaded either
Date: Tue, 4 Jun 2013 22:45:25 -0700
From: [email protected]
To: [email protected]
Subject: the muse file is damaged and cannot be opened
    Re: the muse file is damaged and cannot be opened
    created by Zak Williamson (Adobe) in Help with using Adobe Muse - View the full discussion
Was this file stored in a folder synchronized by Dropbox or any other folder synchronization software?
     Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/5380462#5380462
     Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/5380462#5380462
     To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/5380462#5380462. In the Actions box on the right, click the Stop Email Notifications link.
     Start a new discussion in Help with using Adobe Muse by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

I am unable to open a project that I have worked on and saved. I get an error message that the file is damaged and cannot be opened.

I am unable to open a project that I have worked on and saved. I get an error message that the file is damaged and cannot be opened.

Leslie Tanaka
Travel and detours have kept me from following up sooner. If the problem that you wrote about still persists.....
Let us go back over that Adobe document regarding troubleshooting damaged projects.
3. Delete the Application Preferences
Where you able to follow that path and delete the Adobe Premiere Elements Prefs file at the end of the path? And, after you did, did the saved/closed programs still refuse to open? If you could not carry out this procedure, what were the limiting factors that kept you from do
7. Test to see if individual media files are causing the problem.
That is an important one. How far did you get into following the instructions given in the document? If you could not complete the test, what was the major block that prevented you from doing so?
I want to make sure that we have gone through everything in that document and ruled all factors there in or out. If it was a matter of you not understanding the instructions, I am hoping that the above will channel you questions to me so that I can clarify anything that you did not understand in the Adobe document instructions.
I do not recall if I asked previously. Even if you cannot open all your saved/closed projects, can you still open a new project and save/close it? Maybe even reopen it?
Please review and consider.
Thank you.
ATR

Cannot "print" a window as pdf then read it in Adobe Reader; Adobe says the file is damaged and cannot be opened.

Running Firefox 4.0 on an Intel Mac OS 10.5.8. Same problem with Firefox 3.6.16. You can save a Firefox window as a pdf file by using the File dropdown menu and selecting Print. Under Print, you can select PDF, then Save as PDF or Save as Adobe PDF. Firefox will save the file. If you try to open the file you get an error message that the file is damaged and cannot be opened. I did not have this problem in Safari; I followed the same procedures and the pdf file opened fine in Adobe Reader. Why is Reader rejecting the pdf file produced by Firefox when it did not reject the pdf file produce by Safari?

If anyone is reading this still looking for what caused the issue and how to fix it here is what I discovered.
The antivirus program our company uses, Bitdefender Antivirus Plus, was causing some of the PDF files not to open. After troubleshooting the different modules and settings the culprit was..
Scan SSL in Privacy Control Settings. Turning it OFF solved the problem and all the PDF files that previously would not open now open just fine. This issue has been sent to Bitdefender for them to review. If you use a different antivirus program and are having this issue try locating the Scan SSL setting and see if turning it off solves the problem.

I cannot download Mavericks. Every time the file download stops a message appears that says the file is damaged and cannot be used to install Mavericks. I delete the file, download again and the same message appears. What can I do?

I cannot download Mavericks. Every time the file download stops a message appears that says the file is damaged and cannot be used to install Mavericks. I delete the file, download again and the same message appears. What can I do?

I only have one video project that I ever published to iDisk. It didn't have any music or photo files attatched to it, just a few clips stitched together. I can play these clips right now in the Event Library (so I know the source files are on my computer), but strangely, under the Project Library, the project is not there. I'm almost certain that I didn't store the project on iDisk; I just completed the video and published it to iDisk (as a .mov file I think) for family to see. I've tried to figure out how to get iDisk to stop looking for this project to no avail.
I don't know if others have experienced this, but if I click on any project and on the menu bar select Share --> Remove From --> Media Browser... it lists iPod, iPhone, iPad, tv, Computer and MobileMe. Why would MobileMe be an option here? This is the case for any video project I select. Didn't iLife '11 and/or OSX 10.8 remove all mention of MobileMe? I wonder if this is part of the problem too.
Edit: I just removed every project I have from the Media Browser. Still no luck.

PDF "FILE DAMAGED AND CANNOT BE REPAIRED".

I work at a software firm. We have a web app. Users are complaining that when they download a document in the Web app, they can't use that PDF, as the ERROR Message is "FILE DAMAGED AND CANNOT BE REPAIRED." Known issue. But, how do I fix it. It has to do with encoding and my suggestion is to call the ISP, but is that all that I can do? Is there anything in this forum I can point to?

there is something with the pdf itself that is stopping FF from opening it, as when i try opening the same in Crome ... there also i encounter the same problem (the file opens partially and then stops opening). But if i download the same then i can view the same in Acrobat reader properly.
May be the way the pdf was created used something which FF s not able to render (the graphics used in charts etc)
The work around that is available is that you download the file and save it somwhere, then open the same in Acrobat reader separately

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.

HELP! "This file is damaged and cannot be repaired."

Similar Messages

Maybe you are looking for