Lenovo refused fixing a damage caused by their previous repairing

One year ago, our Lenovo laptop ThinkPad T61 got a replacement of cooling fan at IBM-Lenovo by warranty (laptop was sent to them). Now laptop stopped working (not turning on at all). The warranty is over, so we consulted the local repair company. It occurs that the cover of cooling fan was not installed last time so that the fan eventually cut the wires.
I contacted IBM-Lenovo by phone (1-800-426-7378). I said that IBM-Lenovo should be responsible for the current damage of laptop as it happened because of the service obtained in IBM-Lenovo. From my as loyal customer point of view, such responsibility should be taken regardless of the time when the service was obtained if it resulted in eventual damage. It also should be taken regardless of current warranty status.
However, for all my arguments I received only one answer: "As your warranty expired, you must pay for repair regardless of what caused the damage." I consider such response of IBM-Lenovo representative as inappropriate to the status of the company that intend to keep loyal customers.
What my next steps should be? BBB claim submission?

rc1ph, welcome to the forum,
sorry to hear that your T61 isn't working, would it be possible to post a link to a photo of exactly what you have described and maybe be a little more specific as to which wires were allegedly cut as a result of the repair.
I'll be honest and say that I have replaced plenty of fans in different ThinkPad units and am having difficulty understanding exactly what has happened here.
Thanks in advance
Andy ______________________________________
Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
Deutsche Community Comunidad en Español English Community Русскоязычное Сообщество
PepperonI blog

Similar Messages

What are Apple doing to compensate for the damage caused by the iPhone 4 bumper?

I have noticed damage caused by the bumper.
It is NOT foreign object but caused by the hard plastic on the inside of the bumper
(plese do not come out with rubbish like steel is harder than plastic) I am not stupid and I know that the damage matches the pattern of the bumper skeleton.
What I want to know is when are Apple going to deal with this and replace my phone?
I dare not go to the so called Genius bar in Milton Keynes as they have adopted a Dixons style "fob off" attitude and I will become rather angry with them.

Re: What are Apple doing to compensate for the damage caused by the iPhone 4 bumper?
15-Jun-2011 15:15 (in response to sfrommilton keynes)
o Steel is harder than plastic, so the bumper has not caused the damage.
- You call it rubbish
- The world calls it physics
You are totally wrong. Please go back to School.
o You can deny physics
- but that will not change reality.
You can go to School but that wont change reality.
o Your description of your Genius bar is incomprehensible
- I recommend you go to the Genius bar leaving the chip on your shoulder at home and tactfully explain what you think is your issue.
I recomend you find a day job ans stop TROLLING peoples threads.
- I've never had them fail me or be the least bit confrontational.
- But if you act like a jerk then I couldn't predict what would happen
Yeah because you were there. Are you having some kind of relationship with the company? I think you sleep with an Apple under your pillow.
Finally I am a consumer who has paid for a product that is not living up to expectations. The plastic skelton is hard and abrasive (I know what that means as I went to School) Abrasion's are marking the product.
This is not the only time this has been reported and as such I have no issue with particles entering the bumber. This has happened from the start (when I used Apples stupid bumber case)
Please don't patronise or TROLL others threads.
<Edited by Host>

There was an error opening this document. The file is damaged and could not be repaired. How do I fix this?

I found a resolution, but it is beyond my tdechnical skill without guidance as to where to enter this/how to do this: HKCU\Software\Adobe\(product name)\(version)\AVGeneral\bValidateBytesBeforeHeader=dword:00000000

Problem is not being able to open pdf attachments. Get this error message: "There was an error opening this document. The file is damaged and could not be repaired."
I searched on the web and in the context of a discussion I located, an Adobe professional posted this solution: HKCU\Software\Adobe\(product name)\(version)\AVGeneral\bValidateBytesBeforeHeader=dword:00000000.
I am accustomed to attempting to fix things myself, but I am not a computer science person so it's always a stretch for me. If I get a little guidance I can usually make necessary corrections. I hope that I can with this issue..
Still hoping that someone will know how to fix the error problem which according to what I read is a software issue having to do with the program not understanding something in the pdf header...

Apple says 'damage caused by misuse'. Now what?

Hi there,
Ipod 5th Gen was in my pocket through the day. Went to use it and found the video not working. Screen all garbled = no video, no menu, etc. Apple returned it with a photocopy of a doc saying "caused by accident, misuse or misapplication" and referring me to the web site again. No other explaination or service alternatives.
a) How can it be "accident or misuse"? It was in my pocket.
b) What do I do now?... Buy a new one and only expect 7 months before it breaks?! I fell for that once already. I thought I'd bought a reliable product from a reliable company.
Assistance appreciated.
Ipod 5th Gen Windows XP
Windows XP

Re: What are Apple doing to compensate for the damage caused by the iPhone 4 bumper?
15-Jun-2011 15:15 (in response to sfrommilton keynes)
o Steel is harder than plastic, so the bumper has not caused the damage.
- You call it rubbish
- The world calls it physics
You are totally wrong. Please go back to School.
o You can deny physics
- but that will not change reality.
You can go to School but that wont change reality.
o Your description of your Genius bar is incomprehensible
- I recommend you go to the Genius bar leaving the chip on your shoulder at home and tactfully explain what you think is your issue.
I recomend you find a day job ans stop TROLLING peoples threads.
- I've never had them fail me or be the least bit confrontational.
- But if you act like a jerk then I couldn't predict what would happen
Yeah because you were there. Are you having some kind of relationship with the company? I think you sleep with an Apple under your pillow.
Finally I am a consumer who has paid for a product that is not living up to expectations. The plastic skelton is hard and abrasive (I know what that means as I went to School) Abrasion's are marking the product.
This is not the only time this has been reported and as such I have no issue with particles entering the bumber. This has happened from the start (when I used Apples stupid bumber case)
Please don't patronise or TROLL others threads.
<Edited by Host>

[svn] 4690: * Fixed an issue caused by revision 4330.

Revision: 4690
Author: [email protected]
Date: 2009-01-27 13:12:47 -0800 (Tue, 27 Jan 2009)
Log Message:
* Fixed an issue caused by revision 4330. Due to leaving the backing
variables and functions in the public namespace, they were showing
up in FlexBuilder's code hinting and DataGrid's without specified
columns. Now they are "hidden" in the mx_internal namespace.
tests Passed: checkintests, mxunit databinding
Needs QA: YES
Needs DOC: NO
Bug fixes: SDK-18853, SDK-18604
API Change: NO
Reviewer: Pete F.
Code-level description of changes:
frameworks/projects/framework/src/mx/binding/BindingManager.as
Modified set() to no longer require a userNamespace arg. The
mx_internal namespace is now assumed.
modules/compiler/src/java/flex2/compiler/as3/genext/GenerativeSecondPassEvaluator.java
Renamed makeAttrListPublic() to makeMxInternalAndRemoveOverride(DefinitionNode)
and updated it to handle IdentifierNodes in the
AttributeListNode's items.
Added makeMxInternalAndRemoveOverride(IdentifierNode, Iterator) as
a helper method for common code in
makeMxInternalAndRemoveOverride(DefinitionNode).
modules/compiler/src/java/flex2/compiler/as3/genext/GenerativeClassInfo.java
Modified AccessorInfo's constructor to create a more unique backingPrefix.
Modified getQualifiedBackingPropertyName() to always use the
mx_internal namespace.
modules/compiler/src/java/flex2/compiler/as3/binding/BindableProperty.vm
Modified BindingManager.set() call to no longer pass in the userNamespace.
modules/compiler/src/java/flex2/compiler/as3/binding/BindableFirstPassEvaluator.java
Modified evaluate(Context, ClassDefinitionNode) to add an import
for mx_internal.
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-18853
http://bugs.adobe.com/jira/browse/SDK-18604
Modified Paths:
flex/sdk/trunk/frameworks/projects/framework/src/mx/binding/BindingManager.as
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/BindableFirstPassEval uator.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/BindableProperty.vm
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/genext/GenerativeClassInfo.ja va
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/genext/GenerativeSecondPassEv aluator.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/managed/ManagedProperty.vm

After days of tweaking and suspecting antivirus behind the problems, I reverted back to MSI's default drivers as listed on the product webpage. It appears to be stable so far. Well at least I can use it now.
I'm not sure if Killer's drivers are suck or MSI don't allow drivers 'not certified by them'. But its bad news if someone wants to use the latest drivers considering we're talking cutting edge gaming laptops here.

Fixing a damaged PDF

How could be possible to fix a damaged PDF file ? You would letting me know because this is the third time that I am getting stuck within.
Kind regards,
Masoud Mostafaee

Hi Masoud,
There's no way to fix a damaged pdf via Acrobat.
There are though many 3rd party tools available online that might help.

Damage caused by AT&T installing cable line in my front yard

I am out of town and just received video from my neighbors showing huge equipment parked in my front yard on top of my sprinkler system heads, shrubs, mulch, etc. My front yard is destroyed. My neighbors asked who the workers were and they responded that they work for AT &T and were installing a cable line thru my yard and down the street. I am not a customer of this internet provider and am outraged to not have been given any prior notice that this was taking place. I understand that utility companies have the right of way to certain easements. However, they must repair any damage they cause. I need a contact name and number in Columbia, South Carolina to discuss repairing the significant damage caused by AT&T. If someone from AT&T is monitoring this blog please reply to my message. Thank you

Hello, !
Thanks for posting. I'm sorry to hear about this! We would appreciate the opportunity to look into this, so click here to send us a private message with your contact information, the best time to reach you, and a brief summary of the issue.
You can expect a reply within two business days, so keep an eye on the little blue envelope icon in the top right corner of your screen. In the meantime, feel free to message me with any other questions or concerns.
-Mariana

"The file is damaged and could not be repaired" error when trying to open a PDF in Reader

A few of our employess (only 3 out of over 100 so far) have been getting the error, "The file is damaged and could not be repaired" when trying to open some PDFs. Other people are able to open the same PDF files with no error. It's happening on about 10% of the time. I've read a bunch of threads here with this isue and tried some suggested fixes and nothing has resolved the issue. Here is what I have found works and does not work and the info on their computers:
Computers:
1 Dell Vostro desktop running WIndows 7
1 Toshiba Satellite C55 runnign Windows 8
1 Samsung ATIV Book 4 running Windows 8
All using Adobe Reader XI but we did uninstall that version and tried previous versions and still got the error.
Did Not Work:
As suggested by the company that we use online for claims adjustments where this error is occuring, we tried using a different PDF creator since the files were created using a free PDF creator by the employees. PDF995 and PDFcreator (pdfforge) did not resolve the issue. I then created the PDFs with my Adobe Acrobat, uploaded from my computer to the online program, and that did not resolve the issue.
Saving the file to hard drive and then opening in Adobe did not work.
Turning off Protected Mode and Enhanced Security did not work.
Compatibility View settings enabled in Internet Explorer 10 did not resolve the issue. The previously mentioned claims adjustment software company we use online was code for IE so is not fully compatible with other browsers.
That being said I did try to open the PDF files in Chrome and it also did not work. Same error message.
Does work:
I download the file they cannot open onto my hard drive, open in Adobe Acrobat, Save as a pdf, then email it to them and they can open it via email attachment.
If they close the error and continue trying to open the file over and over sometimes it will eventually open.
Is there a setting in Windows that is preventing them from opening a small % of files some of the time? Thanks in advance for any help!
James

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.

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.

Acrobat 11 there was an error opening this document. the file is damaged and could not be repaired

we are receiving an error when opening certain pdfs saying "there was an error opening this document. the file is damaged and could not be repaired"
i've tried a few things to fix this issue with no luck
tried on a brand new windows 7 install without any added software like anti-virus software, etc
tried on my home pc (I forwarded the document from my work pc to my home pc and still receiving the same error)
don't think it's anything related to the computers, thinking it's more an issue with the pdf. i've tried the basics like deleting temp files from IE, going to %temp% and deleting that out, doing an acrobat repair, trying in reader instead of acrobat, updating users from acrobat 10 to 11, and still receiving the same issue. the odd thing is, some people can open this document and some receive the error. the other thing is i've tried alternative pdf programs with no avail, same errors from those as well
i work on the helpdesk with one other person for the company and not sure what else we can try
don't think this is a pc issue - tried on pcs in the company, home pcs, personal pcs and all get this error
got to be an issue with either the pdf, or the way its being sent
i did reach out to OUR e-mail team here (lotus notes admin) and they've ruled out anything as far as an encryption causing the conflict may go, so notes isn't the issue either
would it be possible it's on the persons end that's sending the file?

Unfortunately, CR 10.5 is not supported on WIN 2012 Server. See this wiki for more details. In order to work in a supported environment you will have to upgrade to CR 2008 Service pack 7, or SAP Crystal Reports, developer version for Microsoft Visual Studio (2010 / 2012 / 2013).
- Ludek
Senior Support Engineer AGS Product Support, Global Support Center Canada
Follow us on Twitter

I keep getting the message, "the file is damaged and could not be repaired"

I have a newer Gateway PC equipped with Windows Vista Ultimate, and recently downloaded the free Adobe Reader 8.1.1 version to it.
I'm not very computer literate, so I'm not sure which terminology to use all the time...sorry.
When I attempt to open (view, read, download?) a pdf file, it starts the download process, showing the progress at the bottom of the page....for example, it might say, "downloading (16.2kb out of 543.5kb)"
Usually, about a minute or so into the download, the word "downloading" changes to "downloaded", the action stops, and shortly after (on the window with the gray Adobe Reader background), a smaller message window pops up, declaring, "the file is damaged and could not be repaired".
A friend suggested that there was probably a problem with the original downloading of Reader and recommended that I completely remove it from my system, then re-install it. Reluctantly, with a very slow dial-up connection network, I did as he suggested, then painfully sat through about a two-hour download AGAIN of Reader 8.1.1
After the download was completed again, I successfully opened a few of the pdf files which I was previously having the problems with. Problem solved??? NOT QUITE!!! After about three or four successful file downloads (openings/readings of the files), it again started to do the same thing, where it would not complete the downloading/opening process and again leaving the message, "the file is damaged and could not be repaired."
I am very confident that the files are not the problem, as many of my friends have viewed/opened those same pdf files repeatedly with no issues, BUT WHAT IS CAUSING THIS??? As I said before, I'm not very computer savvy as it is, and adding the newer Windows Vista Ultimate OS probably hasn't helped any.
1. Is the problem with Windows Vista?
2. Is the problem with Adobe Reader 8.1.1 (or the downloading of it)?
3. Is the problem related to the security settings of my computer?
4. Is the problem likely virus related (I use the purchased McAfee protection)?
I just don't know where or how to start looking for the solution, other than thru this forum, and I simply can't afford the time to remove and re-install Adobe Reader 8.1.1 each time I need the use of my computer.
Any assistance would be greatly appreciated, and you can e-mail me with suggestions to [email protected], or else call me on my cell
THANK YOU,
Don Maycumber
Republic, WA
509-570-8114 Verizon mobile

I'm having the same problem but with high speed access.
Anyone know the answer?
~Chris

Cannot open PDF - "file is damaged and could not be repaired"

We created a signable, saveable, Reader Extended PDF in Acrobat X 10.1.4, with a Submit button that exports it using the "PDF The complete document" format to a .php page on our website using the url: http://www.todayscihld.us/pdfscript/fdf.php?form_name=WebForm
This is the .php page that's supposed to receive the export via the submit button and email it as an attachment:
<?php
// $form_name is provided in the url that calls this page, allowing this page
// to be called from different PDF's, yet customized for each one
$date = (date ("m/d/y"));
$time = (date ("H:i:s T"));
$tmpname = (date ("mdy-His"));
$message = '
This is a multi-part message in MIME format.
------=_NextPart_000_0007_01C37EC6.3F062EA0
Content-Type: text/plain;
    charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
A '.$form_name.' was submitted from the Website at '.$time.' on '.$date.'.
(attachment: '.$form_name.')
------=_NextPart_000_0007_01C37EC6.3F062EA0
Content-Type: application/vnd.fdf;
    name="PDF-'.$tmpname.'.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
    filename="PDF-'.$tmpname.'.pdf"
'.base64_encode(file_get_contents('php://input')).'
------=_NextPart_000_0007_01C37EC6.3F062EA0--
$recip = "[email protected]";
$subject = $form_name;
$headers = "From: Website <[email protected]>\n";
$headers .= "Return-Path: <[email protected]>\n";
//use the following line for bcc:
//$headers .= "bcc: [email][email protected][/email]\n";
$headers .= "Content-Type: multipart/mixed; boundary=\"----=_NextPart_000_0007_01C37EC6.3F062EA0\"\n";
$status = mail($recip, $subject, $message, $headers);
Header("Location: http://www.todayschild.us/page.php?3");
?>
Most of the time this works, however some of the time we get blank PDF files (<10KB), and sometimes we get filled PDF files that we cannot open in Adobe Reader X 10.1.4 - we get the "file is damaged and could not be repaired" error. However, I can view this "damaged" pdf just fine in the Chrome built-in PDF viewer, and I can open it using Foxit Reader and Nitro Reader. And if I open it in one of those programs and then save it under a new name, I can open the newly saved file in Adobe Reader. So why is it that everything except Adobe Reader can open this file?
Here's one of these problem PDF files: https://dl.dropbox.com/u/65535781/PDF-112612-162749.pdf
Can anyone help me figure out what's going wrong, and what we can do to fix it?

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.

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

The file is damaged and could not be repaired.

Hi, I'm debugging an Adobe Drive CC connector and seeking advice on the following problem:
After I check-in an Illustrator file, the local copy becomes corrupt.
If I make a change and try to save it, I receive a message stating "The file is damaged and could not be repaired." If I close the file instead, I can't re-open it (same error message).
However, if I Empty Cache in the Adobe Drive Settings that fixes everything and I'm able to open/save the file without any error. (When I check it in, the same problem repeats itself until I empty cache again).
Where does this message come from and what conditions can trigger it? It's difficult to debug without Adobe's sourcecode to step through the event, but I wonder if it has to do with Etag data?
I've confirmed the stream data downloaded by the open & read handlers is not actually corrupt (by setting a breakpoint after the tempfile is written and checking it's md5).
The problem occurs after every checkin of Illustrator files, but never with Photoshop files.
Any advice? Thanks

I wish I had an answer, but I at least wanted to post in solidaridity and bump this thread. I've been experimenting with Adobe Drive CC (5.0.1.28) and am also suffering from the "file is damaged" issue.
I am using the CMIS connector and after almost every check in or out the file becomes corrupt -- but only in the Drive cache. If I clear the Adobe Drive cache the file is perfectly fine. I have watched the CMIS traffic in Wireshark and it appears to me that this error is entirely within Drive: it does not get a new copy of the file that's corrupted en route, it just corrupts its own copy in the cache.
I experience this with all file types.
Out of frustration I tried Alfresco 4.2.e, which is supposedly the software Adobe worked with to "polish" the CMIS connector, and the problem is entirely different. Every check in failes with "The operation could no be completed because of an unexpected error. Error Code: -1" and a RemoteIOException in the Drive log.
Drive then announces the file "has changed since I opened it, and it will be updated to the newest version" -- which DOES bring new bytes over the wire and avoids the corrupted local cache. Is that somehow the answer the Alfresco has discovered, to break the transaction and force Drive to refresh the file?
Please, anyone, chime in you've experienced either of these issues. I have yet to see a successful use case for Adobe Drive over CMIS, but surely someone is using this product?
Thanks.

Lenovo refused fixing a damage caused by their previous repairing

Similar Messages

Maybe you are looking for