Pdf Not Opening Correctly
I have a problem with a pdf file which does not open with reader in windows 8 but it opens properly with adobe pdf reader. All other pdf can be opened in reader.But when i open a pdf(see this link for pdf for which i got error ) it gives error as 'Can't open this file. There's a problem with file format'. The same file opens properly in adobe pdf reader.You can check the pdf file which i have mentioned in the link above.But the reader which comes with windows 8 can open some other pdf in the same PC.What may be the error causing this?? I have the same problem on most files with the app on Win Phone 8.
PDF created in Foxit will not open in Adobe., 08:13 PM. The file opens correctly in Google's PDF viewer, Foxit, Sumatra.
This always occurs whenever a website generates a PDF file for me. I used Adobe Acrobat X Pro from my Win 7 computer to view the files' security settings. If you go to FilePropertiesSecurity tab, it may show some restrictions in the 'Document Restrictions Summary.' I tested 5 files and found that security settings were enabled for 'Page Extraction'; it shows Not Allowed instead of Allow. Therefore, I was unable to create a new PDF from one of these files. Workaround if you have Adobe PDF software on your computer: Use the XPS printer that is built into Windows 7.
Print the original PDF to XPS format. Then open the XPS file in IE and print to a new Adobe PDF file. I totally agree that something is wrong with Microsoft's PDF app for Windows Phone. It appears that if any of the security options are enabled, then the file won't open. There could also be other settings causing the problem. I'm having terrible problems with the embedded pdf viewer that comes with tile based search. Brand new Windows 8 touch screen machines from Dell, two of them have this problem.
- The Moodle 2 default setting to open PDF files embeds the file. Student need to scroll to view the entire file. However, if they are using a mobile device, they.
- Hi I am 'trying' to help my step daughter with her university online course. When we try to open a pdf file she requires, it states that we require an updated.
You can't open PDFs when using the tile search engine thing. I constantly get 'Adobe PDF viewer not available'.
Really.can't view PDFs using Windows 8? You have to be kidding. The only way to view a PDF is to open the desktop, then open IE, then download a PDF. I've installed Adobe PDF like 3 times. I suggest a Microsoft executive actually try to use the product before allowing shipment, I would die of shame if this were my product.
This has turned out to be an enormous issue for me as I sell PDF files as ebooks. I have done a fair amount of investigating this for my system. My files have to be compatible not just across readers but across operating systems. To date, I have over 200 PDFs that have functioned flawlessly across Mac, PC (Windows 7 and below), Android, iPhone/iPad, Linux. I personally test my PDFs using a variety of readers and PDF editors including. PDF XChange (my favorite). Foxit (runner up for me and I recommend for most people).
Adobe (the bloated monster). Nitro 9 (great for moving graphical elements around). ABBYY.
And the Nuance PDF Create toolsets Those are off the top of my head. There are a bunch on Android that I test with too. I am running the Windows 10 Pro Tech Preview and I have this same problem so I know it isn't fixed yet in any kind of pre-release way (-sigh-) Here is what I've learned for my situation The PDFs I created using NUANCE'S PDF CREATE PROFESSIONAL VERSION 8 all fail using the built-in Windows 8/10 PDF reader. When I look at the PDF properties for these Nuance created files, the underlying engine used to write them is called 'ImageToPDF'. Using ABBYY it indicates their own engine as does everyone else that I've tried.
It is easy for you to check to see what created your PDF by doing a 'Control D' (look at the document properties). Perhaps there's a common engine causing issues. If I use the exact same source files to create a PDF using any of my other tools I have no issues.
I checked the PDF versions made by the tools and they are all set to 1.5. A customer mentioned being able to convert them in a way they worked by saving them without having to do any kind of extraction, but I have not been able to duplicate that. Perhaps he did a 'print' which seems like it could work. In summary, the workaround everyone is talking about, using an alternate reader, of course works. But not everyone wants to change. The culprit I have found is my Nuance PDF Creation tools that are using the ImageToPDF engine. I hope it gets FIXED as I really don't want to have to regenerate all of my PDF files.
It's been 4 months since asking this question, and I still haven't found a good solution. However, I did find a decent workaround, which I will share in case others have the same issue. I will try to update this answer, too, if I make further progress. First of all, my research has shown that there are several possible combinations of user-settings and site settings that cause a variety of PDF display issues. These include:. Broken version of Adobe Reader (10.0.). HTTPS site with Internet Explorer and the default setting 'Don't save encrypted files to disk'.
Adobe Reader setting - disable 'Display PDF files in my browser'. Slow hardware (thanks @ahochhaus) I spent some time researching PDF display options at, which is an EXCELLENT resource and I learned a lot. The workaround I came up with is to embed the PDF file inside an empty HTML page. It is very simple:.
However, here's a list of caveats:. This ignores all user-preferences for PDFs - for example, I personally like PDFs to open in a stand-alone Adobe Reader, but that is ignored. This doesn't work if you don't have the Adobe Reader plugin installed/enabled, so I added a 'Get Adobe Reader' section to the html, and a link to download the file, which usually gets completely hidden by the tag.
In Internet Explorer, if the plugin fails to load, the empty object will still hide the 'Get Adobe Reader' section, so I had to set the z-index to show it. Google Chrome's built-in PDF viewer also displays the 'Get Adobe Reader' section on top of the PDF, so I had to do browser detection to determine whether to show the 'Get Reader'. This is a huge list of caveats. I believe it covers all the bases, but I am definitely not comfortable applying this to EVERY user (most of whom do not have an issue). Therefore, we decided to ONLY do this embedded option if the user opts-in for it.
On our PDF page, we have a section that says 'Having trouble viewing PDFs?' , which lets you change your setting to 'embedded', and we store that setting in a cookie. In our GetPDF Action, we look for the embed=true cookie. This determines whether we return the PDF file, or if we return a View of HTML with the embedded PDF. This was even less fun than writing IE6-compatible JavaScript.
I hope that others with the same problem can find comfort knowing that they're not alone! I don't have an exact solution, but I'll post my experiences with this in case they help anyone else. From my testing, the gray screen is only triggered on slower machines 1. To date, I have not been able to recreate it on newer hardware 2. All of my tests have been in IE8 with Adobe Reader 10.1.2. For my tests I turned off SSL and removed all headers that could have disabled caching. For Win7 Acrobat Pro X Since I did all these without rechecking to see if the problem still existed afterwards, I am not sure which on of these actually fixed the problem, but one of them did.
In fact, after doing the #3 and rebooting, it worked perfectly. FYI: Below is the order in which I stepped through the repair.
Go to Control Panel folders options under each of the General, View and Search Tabs click the Restore Defaults button and the Reset Folders button. Go to Internet Explorer, Tools Options Advanced Reset ( I did not need to delete personal settings).
Open Acrobat Pro X, under Edit Preferences General. At the bottom of page select Default PDF Handler. I chose Adobe Pro X, and click Apply. You may be asked to reboot (I did). I had this problem. Reinstalling the latest version of Adobe Reader did nothing.
Pdf Not Opening Windows 7
Adobe Reader worked in Chrome but not in IE. This worked for me. 1) Go to IE's Tools-Compatibility View menu.
2) Enter a website that has the PDF you wish to see. 3) Restart IE 4) Go to the website you entered and select the PDF.
It should come up. 5) Go back to Compatibility View and delete the entry you made. 6) Adobe Reader works OK now in IE on all websites. It's a strange fix, but it worked for me. I needed to go through an Adobe acceptance screen after reinstall that only appeared after I did the Compatibility View trick. Once accepted, it seemed to work everywhere.
Pretty flaky stuff. Hope this helps someone. Hm, would it be possible to simply do this: The first time your user opens a pdf, using Javascript you make a popout that basically says 'If you cannot see your document, please click HERE'. Make 'HERE' a big button where it will explain to your user what's the problem. Also make another button 'everything's fine'. If the user clicks on this one, you remember it, so it isn't displayed in the future. I'm trying to be practical.
Going to great lengths trying to solve this kind of problem 'properly' for a small subset of Adobe Reader versions doesn't sound very productive to me. Experimenting more, the underlying cause in my app (calling goog.userAgent.adobeReader) was accessing Adobe Reader via an ActiveXObject on the page with the link to the PDF.
This minimal test case causes the gray screen for me (however removing the ActiveXObject causes no gray screen).
Pdf Not Opening On Mac
For a video example of this minimal test case, see. I realize this is a rather late post but still a possible solution for the OP.
I use IE9 on Win 7 and have been having Adobe Reader's grey screen issues for several months when trying to open pdf bank and credit card statements online. I could open everything in Firefox or Opera but not IE.
I finally tried PDF-Viewer, set it as the default pdf viewer in its preferences and no more problems. I'm sure there are other free viewers out there, like Foxit, PDF-Xchange, etc., that will give better results than Reader with less headaches. Adobe is like some of the other big companies that develop software on a take it or leave it basis. So I left it. We were getting this issue even after updating to the latest Adobe Reader version. Two different methods solved this issue for us:. Using the free version of Foxit Reader application in place of Adobe Reader.
Pdf Files Not Opening Correctly
But, since most of our clients use Adobe Reader, so instead of requiring users to use Foxit Reader, we started using window.open(url) to open the pdf instead of window.location.href = url. Adobe was losing the file handle on for some reason in different iframes when the pdf was opened using the window.location.href method.