There was an error opening this document. Adobe Reader XI

Win Xp, Sp 3. When converting a word-dokument with Acrobat Elements 7.05 the immediately opening in Adobe Reader XI fails with several of the "well known" messages "There was an error opening this document. File not found" and "There was an error opening this document. Access denied" (translated from Danish).
The fix by setting this registry entry:
[HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\11.0\Privileged]
"bProtectedMode"=dword:00000000
seems to help. But is that a sane solution?

Hi P.Allan,
By making the registry setting entry:
[HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\11.0\Privileged]
"bProtectedMode"=dword:00000000
Reader will become unsecure.
Please make it back to 00000001 to make Reader more secure.
Also, please let me know the following:
1) Is the converted PDF got saved?
2) If yes, please let know the path where it get saved?
3) If yes, can the converted PDF file be opened in ReaderXI from next time?
Thanks
Shakti

Similar Messages

"There was an error opening this document" Adobe PostScript Driver creates corrupt PDF's.

Hello,
Just looking for a point in the right direction or some answers to a problem that has been plaguing a few of our users.
We use Adobe reader X and Adobe Post Script driver as a means to print a document as a PDF.
However, a few of our users are experiencing the problem where as the every so often a PDF created comes up with the "There was an error opening this document. The file is damaged and could not be repaired." Message. these documents always vary in size but average around 20 - 30 kb, These seem to be complete anomolies and are corrupted from the off. The only solution we have found for this is a complete rebuild. But we have no idea what is causing this, as we are using the latest version of Adobe Reader. Also, a document that will print corrupted on one go, will print fine on the next.
Thanks.

Hi Lori,
Thanks for your reply currently all users access these PDF's through the standalone reader and users on the most up to date version of Adobe Reader X are not using protected mode as we have had it turned off for a while to fix other problems.
Thanks

With OSX10.7.5 and Adobe Reader 11.0.02 when I try to open a PDF downloaded from the web I get 'There was an error opening this document. This file is damaged and could not be repaired. Preview will not open either. Older PDFs OK.

I am running OS X 10.7.5 and Adobe Reader 11.0.02. In the last few days I have been unable to open PDF's downloaded from the web. Reader gives the error message 'There was an error opening this document. The file is damaged and could not be repaired'. Removing Reader and trying to use Preview to open these files give the error 'Preview cannot open this file. It may be damaged or use a file format that Preview doesn't recognise' (or something like that). Downloading the same files with Reader removed from my Mac Preview opens the files OK.
I was recently prompted to update Adobe software but did not note exactly what the update was nor when it was done.
Reader and Preview will both open PDFs I downloaded a week ago. Reader will also open files downloaded on another Mac running OS X 10.0.0 and copied to my Mac. Any ideas?

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.

Adobe Reader 11.0.06 "There was an error opening this document. Access Denied"

Windows 7 64-bit
If I go into My Windows 7 Documents Library folder (which is redirected by Group Policy to a network share), I get "There was an error opening this document. Access Denied". If I then map a drive to the share, I can open the PDF without the error message.
I've read a workaround for some time now for older versions has been to uncheck Enable Protected Mode at startup under Security (Enhanced) in Preferences. I find this does work but this is probably not the best way to handle this situation.
I've also read one person removed the desktop.ini on the desktop to resolve.
Is there any official response from Adobe on this issue that I can be pointed too? Are others still having this issue?
We plan to update several thousand clients and I'd like resolve this issue before we do.

We tried 11.0.05, 11.0.06 and 11.0.07 with the same result on different computers with different local Admin accounts.
When we re-install 10.1.0 the issue is gone and Protected Mode is enabled.
We then returned to 11.0.06 or 11.0.07
I'm logged in with a local Admin account.
I turned on Protected Mode Logging and captured what happens when I attempt to double click a pdf file in my Documents Library with 11.0.06 installed. Access Denied.
I then doubled clicked the file from a drive mapped to the same share and the file opened.
[06:11/16:02:40] Adobe Reader Protected Mode Logging Initiated
[06:11/16:02:41] NtCreateKey: STATUS_ACCESS_DENIED
[06:11/16:02:41] real path: \REGISTRY\MACHINE\Software\Adobe
[06:11/16:02:41] Consider modifying policy using this policy rule: REG_ALLOW_ANY
[06:11/16:02:41] NtCreateKey: STATUS_ACCESS_DENIED
[06:11/16:02:41] real path: \REGISTRY\MACHINE\SOFTWARE\Wow6432Node\Adobe
[06:11/16:02:41] Consider modifying policy using this policy rule: REG_ALLOW_ANY
[06:11/16:02:41] NtCreateFile: STATUS_ACCESS_DENIED
[06:11/16:02:41] real path: \??\Volume{a758d00a-e81c-11e2-b856-806e6f6e6963}\$Extend\$Reparse:$R:$INDEX_ALLOCATION
[06:11/16:02:41] Consider modifying policy using these policy rules: FILES_ALLOW_ANY or FILES_ALLOW_DIR_ANY
[06:11/16:02:41] NtCreateFile: STATUS_ACCESS_DENIED
[06:11/16:02:41] real path: \??\UNC\nawrcs-bbc1fs\mousers\u212940\Documents\Citrix Adding a Printer.pdf
[06:11/16:02:41] Consider modifying policy using these policy rules: FILES_ALLOW_ANY or FILES_ALLOW_DIR_ANY
[06:11/16:02:41] NtCreateFile: STATUS_ACCESS_DENIED
[06:11/16:02:41] real path: \??\UNC\nawrcs-bbc1fs\mousers\u212940\Documents\Citrix Adding a Printer.pdf
[06:11/16:02:41] Consider modifying policy using these policy rules: FILES_ALLOW_ANY or FILES_ALLOW_DIR_ANY
[06:11/16:02:46] NtCreateKey: STATUS_ACCESS_DENIED
[06:11/16:02:46] real path: \REGISTRY\USER\S-1-5-21-1691402968-2266345157-3523873211-67461\Software\Adobe\Adobe Acrobat
[06:11/16:02:46] Consider modifying policy using this policy rule: REG_ALLOW_ANY
[06:11/16:02:46] NtCreateKey: STATUS_ACCESS_DENIED
[06:11/16:02:46] real path: \REGISTRY\USER\S-1-5-21-1691402968-2266345157-3523873211-67461\Software\Adobe\Adobe Acrobat
[06:11/16:02:46] Consider modifying policy using this policy rule: REG_ALLOW_ANY
[06:11/16:02:46] NtCreateKey: STATUS_ACCESS_DENIED
[06:11/16:02:46] real path: \REGISTRY\USER\S-1-5-21-1691402968-2266345157-3523873211-67461\Software\Adobe\Adobe Acrobat
[06:11/16:02:46] Consider modifying policy using this policy rule: REG_ALLOW_ANY
[06:11/16:02:46] NtCreateKey: STATUS_ACCESS_DENIED
[06:11/16:02:46] real path: \REGISTRY\USER\S-1-5-21-1691402968-2266345157-3523873211-67461\Software\Adobe\Adobe Acrobat
[06:11/16:02:46] Consider modifying policy using this policy rule: REG_ALLOW_ANY
[06:11/16:02:46] NtCreateKey: STATUS_ACCESS_DENIED
[06:11/16:02:46] real path: \REGISTRY\USER\S-1-5-21-1691402968-2266345157-3523873211-67461\Software\Adobe\Adobe Acrobat
[06:11/16:02:46] Consider modifying policy using this policy rule: REG_ALLOW_ANY
[06:11/16:02:46] NtCreateKey: STATUS_ACCESS_DENIED
[06:11/16:02:46] real path: \REGISTRY\USER\S-1-5-21-1691402968-2266345157-3523873211-67461\Software\Adobe\Adobe Acrobat
[06:11/16:02:46] Consider modifying policy using this policy rule: REG_ALLOW_ANY
[06:11/16:02:46] NtCreateKey: STATUS_ACCESS_DENIED
[06:11/16:02:46] real path: \REGISTRY\USER\S-1-5-21-1691402968-2266345157-3523873211-67461\Software\Adobe\Adobe Acrobat
[06:11/16:02:46] Consider modifying policy using this policy rule: REG_ALLOW_ANY
[06:11/16:02:46] NtCreateKey: STATUS_ACCESS_DENIED
[06:11/16:02:46] real path: \REGISTRY\USER\S-1-5-21-1691402968-2266345157-3523873211-67461\Software\Adobe\Adobe Acrobat
[06:11/16:02:46] Consider modifying policy using this policy rule: REG_ALLOW_ANY
[06:11/16:02:47] NtCreateFile: STATUS_ACCESS_DENIED
[06:11/16:02:47] real path: \??\C:\Users\c702939\AppData\Local\Microsoft\Windows\Caches\cversions.1.db
[06:11/16:02:47] Consider modifying policy using these policy rules: FILES_ALLOW_ANY or FILES_ALLOW_DIR_ANY
[06:11/16:02:47] NtCreateFile: STATUS_ACCESS_DENIED
[06:11/16:02:47] real path: \??\C:\Users\c702939\AppData\Local\Microsoft\Windows\Caches\cversions.1.db
[06:11/16:02:47] Consider modifying policy using these policy rules: FILES_ALLOW_ANY or FILES_ALLOW_DIR_ANY
[06:11/16:02:47] NtCreateKey: STATUS_ACCESS_DENIED
[06:11/16:02:47] real path: \REGISTRY\USER\S-1-5-21-1691402968-2266345157-3523873211-67461\Software\Adobe\Adobe Acrobat
[06:11/16:02:47] Consider modifying policy using this policy rule: REG_ALLOW_ANY
[06:11/16:02:47] NtCreateKey: STATUS_ACCESS_DENIED
[06:11/16:02:47] real path: \REGISTRY\USER\S-1-5-21-1691402968-2266345157-3523873211-67461\Software\Adobe\Adobe Acrobat
[06:11/16:02:47] Consider modifying policy using this policy rule: REG_ALLOW_ANY
[06:11/16:02:47] NtCreateKey: STATUS_ACCESS_DENIED
[06:11/16:02:47] real path: \REGISTRY\USER\S-1-5-21-1691402968-2266345157-3523873211-67461\Software\Adobe\Adobe Acrobat
[06:11/16:02:47] Consider modifying policy using this policy rule: REG_ALLOW_ANY
[06:11/16:02:47] NtCreateKey: STATUS_ACCESS_DENIED
[06:11/16:02:47] real path: \REGISTRY\USER\S-1-5-21-1691402968-2266345157-3523873211-67461\Software\Adobe\Adobe Acrobat
[06:11/16:02:47] Consider modifying policy using this policy rule: REG_ALLOW_ANY
[06:11/16:02:47] NtCreateFile: STATUS_ACCESS_DENIED
[06:11/16:02:47] real path: \??\C:\Users\c702939\Desktop\desktop.ini
[06:11/16:02:47] Consider modifying policy using these policy rules: FILES_ALLOW_ANY or FILES_ALLOW_DIR_ANY
[06:11/16:02:48] NtCreateFile: STATUS_ACCESS_DENIED
[06:11/16:02:48] real path: \??\C:\Users\c702939\Desktop\desktop.ini
[06:11/16:02:48] Consider modifying policy using these policy rules: FILES_ALLOW_ANY or FILES_ALLOW_DIR_ANY

Adobe reader: there was an error opening this document. this file cannot be found.

Windows XP Professional sp2 machine
512 memory
ie sp2
when opening two pdfs from a website links receive the error, "there was an error opening this document. this file cannot be found"
If you save the file to the pc, then open the .pdf it opens ok
other pdfs open ok from browser from same website and different websites
had customer try on another's machine; the two pdfs opened ok
tried Adobe Reader 8.1, 9.0, and Adobe Professional 8.0
uninstalled reader and professional; deleted directories; reinstalled reader and professional(placed into a separate directory); same error
On the machine tried admin accounts, under customer's profile made admin account, renamed the customer's account so that another account was freshly generated, all generated the same error.
Ran ccleaner to clean up files in the registry and temporary internet files, then repaired adobe - same error
repaired internet explorer - same error
scoured web for same error but most were applications trying to open the pdfs, a few errors were for programming php, a lot of questions but few answers in context of current issue. the ccleaner and repairing ie were resolutions i found on the web.
nothing was listed in msoft's ie knowledgebased searched.
any help would be appreciated.

I get the same message when I try to open a pdf attachment in my free AOL e-mail account. This problem just started today for some unknown reason. I have Adobe Reader 9 and never had a problem before. If I forward e-mails with a pdf attachment to my Road Runner account, I can open it with no problem. I can't seem to find any answers to this problem. Frustrating! HELP!!!

"there was an error opening this document the root object is missing or invalid" adobe reader 9

I get the following message every time I try an open some of my saved PDF files in Adobe Reader 9
"there was an error opening this document. the root object is missing or invalid."
these files are not down loaded from a website, they are files I greated some time back and I have not opened in a while.
I am runing window XP and this dos not happen with all my PDF files.
can you help.
James

Sounds like the files are corrupt. Time to restore them from a good backup.

Adobe pdf problem; the message comes up:- There was an error opening this document. The file is damaged and could not be repaired.

Dear all
I have got 3 mac computers. 2011 13 inch air, 27 inch mac and 2010 pro. latest softwares. all of them have a problem in opening pdf files;esp older files. the error message comes up 'There was an error opening this document. The file is damaged and could not be repaired.'
I have reinstalled reader, checked software updates etc.
Any help will be appreciated

It isn't likely to be a problem with the software. You have two different applications which have no interaction between them, neither of which can open the same group of files on three different systems. It's possible that one application has a problem, but not both or that one system has a problem, but not all three. Typically if there were software corruption, it would not show as a failure to open a specific type of file, but in opening and running the application itself.
I realise that that doesn't really help you since it doesn't resolve the poblem, but I think you need to start with a known-good pdf, preferably one you can download from an internet source, and see whether that opens. If it does, then it would confirm that the software is working properly.
For a known-good PDF to download, try one of the manuals from the support site here.

There was an error opening this document. Access denied.

Greetings,
When I did my taxes last year (March 2012), I downloaded some pdf files from the IRS. Form 1040 was a writable file and I filled it out as needed. This file was saved on a Vista machine running XP. A few months ago, I upgraded that pc to be Windows 7 SP1.
Today I'm getting ready to do my taxes for this year. When I double click on last year's Form1040.pdf, I get the following error message:
There was an error opening this document. Access denied.
Interestingly, I can open other pdf files, like the Form 1040 Instructions. I do not think that I password protected my Form1040.pdf. The reason that I think it isn't password protected is because I'm not being prompted to enter a password.
I copied the file to an old spare XP machine (XP Home, version 2002, SP3) that I have and it opened fine. It did not prompt for a password. I printed copies of last year's forms from that XP machine, so this isn't an emergency for me, but it is mildly annoying that I can't figure out what's wrong.
I have Adobe Reader XI version 11.0.2 installed on both machines (the Windows 7 machine and the old XP machine).
To summarize, it was created on Vista, I can't open it with Windows 7, but I can open it with XP.
Normally I would consider uploading the file in question, but in this case, I hope you'll agree that might be a bad idea!
Advice on how to get this to work on Windows 7 would be appreciated.

Pat Willener: Thanks! That solved the problem.
For anyone else having this problem, here's a detailed list of how I used Pat's advice to solve my problem:
1. Right click on the problematic file
2. Select Properties
3. Select the Security tab
4. Press continue
5. In the "Permissions for MyFile.pdf" dialog, press "Add".
6. In the "Select Users or Groups" dialog, press "Advanced".
7. The next dialog that pops up is also named "Select Users or Groups". Press "Find Now".
8. Scroll down the list of search results until you find your username.
9. Double click on your username.
10. Press ok in the "Select Users or Groups" dialog.
11. Press ok in the "Permissions for MyFile.pdf" dialog
12. Press ok in the Properties dialog.
done.

With Reader XI There was an error opening this document. Access denied

Hi there, It looks like I have a simular problem. I also get the error "There was an error opening this document. Access denied." This when I tried to open the file by clicling on the file. When I try to open the file from out Adobe reader it gives me the error "You don't have permission to open the file" I use Adobe XI. My OS is W8.1 By clearing protected mode doesn't help. This is what I found sofar: Only the PDF files in the documents and subfolders are giving me this error. PDF files in other folders are fine. When I copy PDF files from the documents folder to Desktop they open without any problem. First I thought I might be a permission problem with the Documents folder, but I have full access. Other files in the Documents folder like Word and Excel files open fine with MS Office. My laptop has WinXP and is shared with my PC when I open PDF files on my laptop by using the network share they open without problems. So it looks like only the PDF files in my Documents folder. I'm not sure but before upgrading to W8.1 from W8.0 I can't remember if I had this problem, but I think I did not have it. To make it even more interested is that I have also Adobe Acrobat Writer on my PC what I use for my buisiness. When I open the PDF files with this program they open without any problem. Therefore I believe it is not a permission problem, I still believe it is a problem with Reader XI, but than only after upgrading to W8.1, but as I already mentioned I'm not sure for 100% only that sofar I know it never happened under W8. Has anyone out there simular problems? And hopefully with a fix.

This is what I did sofar: Deleted reader XI and reinstalled same problem.
Because I think the problem is with reader XI I deleted again XI and installed reader X.
With this version I can open PDF files located in the documents folder without any problem.
For now I keep using version X until they fixed version XI
This proves that reader XI will not work under W8.1 when opening PDF files in de documents folder.
Bennie

Another "there was an error opening this document. this file cannot be found"-question

Hello people, as the title suggests, i have another question regarding the "there was an error opening this document. this file cannot be found" error. I have searched on Google and on these forums but i havent found an answer to my particular case (sorry if i overlooked it).
I work at a supportdesk for a company that uses Windows XP with Adobe Reader version 8.1.3.
Users are getting this error when they access a PDF file placed on a (mapped) networkdrive. Contrary to some other cases i have found on this forum, spaces are handled without a problem. But a comma in the name of one of the folders that contain the PDF file are what causes this error.
i.e.:
Opening the following path results in the error:
L:\X, Y & Z\adobe.pdf
Removing the comma so the path becomes:
L:\X Y & Z\adobe.pdf
works just fine.
So far our workaround has always been to simply remove the comma and move on, but I've been wondering why this comma is such a problem for Adobe Reader. As far as i know Adobe Reader is the only program we use that has this issue, M$ Word works just fine with it to name an example.
To sum my questions up:
- Why is comma (,) a problem for Adobe Reader?
- Have i missed any patches/new versions where this issue has been addressed?
- What is Adobe's stance on this, and are there any plans to "fix" this?

Ok, nevermind, we just found the problem
It's not Adobe Reader that is causing this, but another program the company uses to manage/distribute/authorise programs that users are allowed to access (Scense). I had never even considered another problem could have caused this for Reader.

Message'there was an error opening this document.The file cannot be found'

Using xp home and when I click to download the pdf file, it will give 3 options been 'open'/'save'/?. When I choose the 'open' option, it will give me the above message "there was an error opening this document.The file cannot be found"
owever if I choose to "save" and I will be able to open the file and read it. In this pc its using Adobe Reader 8.1.2 with a patch. It was working fine prior to this sudden occurance of the error.
Strangely I have another pc with the same specification, I was able to choose "open" and be able to read the file. Can anyone help to resolve the issue by using the "open' option instead of "save, then open". Greateful for your prompt response.

Fyi, in addition to my earlier post, the other pc is using Adobe 8.1.1 and no other patch. I was trying to find 8.1.1 version but could not find a trust worthy site to load from. Do you think the error caused by using the 8.1.2 version? Thanks

There was an error opening this document. This file cannot be found

An automation script on one of our QA environments kept tripping on the error: "There was an error opening this document. This file cannot be found". The same script ran fine against our Production servers (hint, which were "whitelisted").
It took a little time to resolve/trace what was happening (but with the aid of ProcessMonitor and tracing all "pdf"-related file activity...)
The problem lies squarely between McAfee (75%), Adobe (20%) and Microsoft (5%):
NORMAL WORKFLOW. IE (Internet Explorer) when popping a PDF document, has to (1) write the document to the IE cache, then (2) launching and "handing off" the document reference to the Adobe viewer (which might then be able to open the document, et al) -- assuming largely a "synchronous" workflow.
BUT "WAIT", HOLD THE HORSES -- McAfee takes ownership and decides infact "wait for us" (during the workflow), it wants to first perform a virus scan on the document (ahead of writing the document to cache) involving potentially large latency (delay) before making the document available to the system. However, instead of "fessing up"-that their scan may be taking too long, McAfee appears to have taken their work "off-line" in violation of the sychronous interface above. I'm guessing the developers at McAfee might have been trying to hide any extra processing overhead being incurred by assuming they could somehow convert this to an "asychronous" event. (This may also have more reach than just PDF's.)
Unfortunately, the browser's "PDF OPEN"-dialog box pops allowing Adobe to launch-and-open the "as-yet-not-virus-scanned-and-thus-not-yet-cached"-document. Thus clicking the OPEN-button will cause the related "...FILE NOT FOUND"-error to be seen (because the file is still in McAfee "limbo").
Note: If you close the ADOBE reader (but don't yet close the popup-OPEN-dialog) you can click OPEN a second time and it will probably now open the document - which McAfee finally finished scanning!
You can observe all these interactions with ProcessMonitor, and use the monitored file states to adjust the timings of events to reproduce both the failure and non-failure scenarios.
- Best Regards, Ziggy
ps. My assessed distribution of "ownership" of the problem is because ALL these parties should be aggressively resolving this for the customer-base!

What, exactly, were you trying to do when you got it, and how?

"There was an error opening this document. The filename, directory name, or volume label syntax is i

"There was an error opening this document. The filename, directory name, or volume label syntax is incorrect."
I tried different versions, no avail.
I think it has to do with the password somehow, but I do not know. I can copy the files from the web folder to my desktop and they open fine (after entering the password AGAIN), but I can not open them directly form the web folder - it does not ask for the password again, just pops up the error.
Adobe's support really upset me (insert explicative here) by keeping me on the phone for 20 min, collecting all sorts of information about me (not the problem) with some lady who barely spoke English, just to tell me to go to the website. No surprise they need to charge for tech support, customer service is doing everything but "service". I hate companies that do this. I am thinking of using another PDF reader, I have heard good things about them. Check
http://en.wikipedia.org/wiki/List_of_PDF_software
Has anyone ever been able to find a fix? I can not find anything on this site.

Howdy, Moritz!
Thanks for the suggestion, but this is not an issue of filename and language conflicts, at least in my environment. I highly doubt that's the root cause of this issue.
The PDF files in my tests have all had very simple names, such as 123.pdf and test.pdf, as well as more complicated names with spaces in them. Nothing about the files contains anything outside of the English language, including the content and filenames.
From everything I've been able to determine, this is a WebDAV-related security issue that affects programs like Acrobat Reader. I know for a fact that MS's KB892211 WebDAV patch doesn't create the issue, however MS's update to that 892211 patch DOES create the issue. As I've outlined earlier in this thread, my extensive testing has proven this more than once.
At this point, I haven't been able to accurately uninstall the update to 892211 after the update has been installed. And, as far as I can tell, the update to 892211 comes down from MS as a Office and/or Windows Update component. So, everyone has it, the uninstaller doesn't work, and there's no documentation detailing what registry entries are being changed when the update to 892211 is installed.
My ultimate goal is to bring a test machine to the point just before the update to 892211 goes on, fire up the Registry, Process, and File monitors on my test box, and install the 892211 update. This should give me an accurate picture of what I need to restore in order to rid the machine of the update to 892211.
Until Microsoft officially fixes the issue, I am not totally sure how this will be resolved. I've ceased my work on the issue for now since copying the PDF file from the WebDAV share to the user's desktop gets the user what they wanted in the first place - the ability to open the PDF file!
Maybe, once some other projects slow down a bit, I might get back to creating a solution, but it's going to be a "hack" no matter which way you slice it. I'd much rather MS spend their time creating the solution. If I have to do it, my fee to MS will be quite HIGH! :*)
George B.

There was an error opening this document. The file is damaged and could not be repaired.

Good Day all
When busy doing internet banking on www.absa.co.za and I try to print a confirmation, I get the following error message: "C:\Documents and Settings\%user profile%\Local Settings\Temporary Internet Files\Content.IE5\%folder name%\%file name%.pdf
Could not open file.
File not found."
I've managed to locate the actual file that it's looking for, but when I try and open the file using either Adobe or Foxit Reader, I get the following error message: "There was an error opening this document. The file is damaged and could not be repaired."
I've un-installed Adobe and installed version 9.1 for this particular user. This happened a while ago and then an un-installation and re-installation of Adobe solved the issue. This time, unfortunately, it didn't. I then un-installed Adobe and tried again, UNSUCCESSFULLY. So I loaded Foxit Reader, also without any success.
If there's anyone out there who could possibly help, please do so... It's extremely urgent.
Please find the errors attached as well.
Regards,
ME

I contacted the company and they asked me to try using another browser, which I did... and using FireFox worked
thanks for the help ʇɐb ɹəuəllıʍ
cheers!

I'm having trouble accessing my pdf. Error message: "There was an error opening this document..."

Hi
I have been working on a pdf in Adobe Reader 9.3 on 2007 Microsoft Windows v5.1. The pdf is set up as a form that I can enter data into. Last time I worked on it I saved it, and then when I went to open it the next time I had the following error message: "There was an error opening this document. There was a problem reading this document (14)."
I have tried to recover the pdf by going to www.datanumen.com/apdf but when I try to repair the pdf I get another error message: "Xml parsing error: not well formed (invalid token) (error code 4), line 12874, column 20 of file." The second error message looks like the problem has been pinpointed but I don't know how to fix it.Could you please let me know if there is any way to recover this file?
Thanks to anyone who can point me in the right direction!!

Thanks for the information.
Could you please also let me know which version of Adobe Reader are you currently using. If you are not using Reader 9.4.6 (which is the latest version of Adobe Reader), can you try updating to the latest released version by
1. Launching Adobe Reader
2. Clicking on Help > Check for Updates
3. When prompted click on Download followed by Install.
This will update Reader to the latest version.
Also, please verify if this issue that you are facing is with a specific PDF alone or is the issue happening with all PDFs that you are trying to print from Win7.
Ankit

There was an error opening this document. Adobe Reader XI

Similar Messages

Maybe you are looking for