Adobe Reader X and Page Embedded PDFs

I think I solved the problem for my website my turning off gzip compression for pdf files in my htaccess file

SetOutputFilter DEFLATE

SetEnvIfNoCase Request_URI \.pdf$ no-gzip dont-var

Taken From:

http://www.mybelovedphp.com/category/apache/

Hope that helps someone!

We are a large organisation now faced with what appears to be yet another Adobe Reader X issue. With 10.0.0 and 10.0.1, all was fine. With the release of 10.1.0 and 10.1.1 our Adobe interactive forms would load extremely slowly and be impossible to navigate, or lose all data when users tried to submit them online. For example, a business process that should take 1 minute was taking end users 45 minutes to complete. Needless to say, our end users were extremely unimpressed.

When 10.1.2 came out after a 3 month wait, those performance issues appeared to be resolved when we tested it, and our credibility seemed to be on the mend, but that appears to be short lived and premature. Now, the forms don't even load at all on some end user systems, with a grey screen, a blue bar and a message similar to 174kb/0kb loading. It never completes loading and stays stuck on 0kb, and the Adobe Interactive Form does not appear. F5 refresh does not work, and working on the PDF offline as a saved file is not an option. Like J.Perkinson, I have tried all the suggestions except for the registry, as the PC's belong to end users in the public domain. We are limited to what we can advise our end users because they have such disparate systems (XP, Vista, 7), browsers (IE7, IE8, IE9), Adobe Reader( 8, 9 10/X) and we are fast approaching a situation where each Adobe Reader version has particular quirks and settings that just confuses the end user and further undermines our credibility.

Whilst reverting to Adobe Reader 9.4 or 10.0.0 or 10.0.1 will solve their problem in our case, the end users are reluctant to roll back their Adobe Reader installations for security reasons. We don't want to be responsible for causing a security breach and ending up facing legal action. A high percentage of our end users are in the legal profession, so we definitely don't want to go there :-)

Our PDF's generated with https:and extensions of PDF.

Frustratingly, some users of IE7 and AR 10.1.2 are not having issues, yet others are. It is a similar story on IE8 and AR 10.1.2. Some have fresh installs of AR 10.1.2, whilst others have been progressively been upgrading since 9.x. I am at a loss as to what to do other than hope that Adobe takes notice and action on this forum.

I am yet another person with the same issues with gray screens until refreshed with streamed PDFs.  On Windows 7 32 bit with ie9 and Adobe plugin version 10.1.2.45 (Adobe reader itself shows 10.1.2).  Having them open directly in Adobe does work, it just gets the gray screen in IE until they refresh (F5).  I have tried the fixes above except for the registry (as they don't seem to apply) and uninstall/reinstall (as these are fresh installations) fixes with no luck.  These are new builds with fresh Adobe X installations.  The pdfs are generated with http: and extensions of .pdf.

I was experiencing the same issues with adobe X and tried numerous solutions mentioned.  Nothing worked.  Adobe released a new version this week.  Today, I updated adobe to version 10.1.2.45.  This fixed my problem.  I am now able to view pdfs in the browser without receiving the blank gray background.

Here is the solution I found:

http://itissolved.blogspot.com/2011/03/adobe-x-not-opening-pdf-in-ie-window.html

It worked for me.

summary:

1. Open Adobe Reader X.

2. Press "Ctrl K" (Edit=>Preferences)

3. Select General Category from the left pane

4. Uncheck the "Enable Protected Mode at Startup" checkbox

5. Click on "Internet" in the left pane

6. Uncheck everything in the window EXCEPT "Display PDF in browser"

7. Press "OK"

8. Close Adobe X and try to open the document again.

It may not be necessary to uncheck all of these items but this is what we did and it resolved the issue.

We've run into this issue also. We have been streaming pdfs to our clients with no issues until somebody got a new laptop with Adobe Reader X. We've used various suggestions to get a partial menu back (don't run in protected mode, don't display in read mode by default). However, no matter what we try we can't get menu options to print or save. All we can do is tell them to right click the pdf to get the print option and to type Shift-Ctrl-S to save. Neither is as convenient as what we had up through version 9.4. Version 10.1 may have helped some people but it hasn't helped us. For now, we are discouraging our clients from upgrading Adobe Reader but that is up to their IT departments. We are really hoping Adobe does something to get the IE plugin to work like it used to. This is making things look bad for both Adobe and us.

I was having an issue with a red x appearing in IE8 (32-bit) on Windows 7 (64-bit) when trying to view embedded PDFs.  The addon had installed and was showing up in the list of addons for IE8, but the addon would never load, leaving a red x.  I checked the DLLs loaded into the IE process and noticed that only a AcroIEHelper and AcroIEHelperShim files had loaded.  I tested on a working machine and there were a few more Acro dlls loaded.  I assumed the shim was failing to load the correct DLL.  It turned out I was missing a registry key that was pointing to the AcroPDF.dll that is required by the plugin.  To fix it, I added the following to my registry (Window 7 x64):

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Ext\Stats\{CA8A9780-280D-11CF-A24D-444553540000}]

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Ext\Stats\{CA8A9780-280D-11CF-A24D-444553540000}\iexplore]
"Type"=dword:00000001
"Flags"=dword:00000000
"Count"=dword:00000003
"Time"=hex:db,07,08,00,01,00,0f,00,10,00,0e,00,32,00,05,02

I added the same set of keys in my HKEY_USERS section (same path, but with the user id added between HKEY_USERS and Software).

This fixed the issue on my machine, and it loaded the embedded pdf next time I tried opening one in IE8.

NOTE:

{CA8A9780-280D-11CF-A24D-444553540000} is the Class ID for my installed AcroPDF plugin.  It may be different on your system depending on the version of Reader you have installed.  You should replace it with your Class ID which you can find with the following method:

• Open IE
• Go to "Tools"->"Manage Add-ons"
• Change "Show:" to "Run without permission"
• Right click on "Adobe PDF Reader"
• Click "More Information"
• The information is in Class ID

Hopefully this will help someone.  I know I wasted nearly a day of development time trying to work through this issue.

Message was edited by: wolfzombie

(DYNAMIC PDF-Streamed PDF- EMBED PROBLEM SOLUTION...)

Hi, everyone,

I had been experiencing the same problem for a long time..I had been googling, searching in lots of forums. I found the solution...Here it is:

*** The problem occurs -as mentioned in previous messages- when DYNAMIC PDF is the case...Static PDF is always OK...But like me, lots of programmers, in .JSP servlets or whatever
, sends the generated PDF to the client browsers as a STREAM...That is DYNAMIC PDF.

*** The problem is not because of ADOBE READER or sth. It is because of INTERNET EXPLORER....In firefox there is no such problem....As I learned, IE don't look at the concent type
header like "application/pdf" to understand the content....But it definitely looks the URL ending...if it ends with ".PDF" then IE thinks that incoming stream is PDF content then it calls the ABOBE READER plugin...
Then problem disappears....

*** So, the solution is: Change the URL, to end with "http://.......pdf" then it will be OK....

*** In my case, the URL was "http://servername:serverport/contextroot/ViewDoc.jsp&docid=12345"    like this....

I only, programatically, added to end of URL, the fake string :          "&a=a.pdf"

so url became ; http://servername:serverport/contextroot/ViewDoc.jsp&docid=12345&a=a.pdf         ...........that's all....it always works nowwwwwww...

IE now looks at the URL and sees that that ends with ".pdf" and thinks that incoming stream content is PDF then calls ADOBE READER plugin and shows the pdf content in browser...

(I tested this on IE6 and IE7,,,but later versions will be OK,too  I guess..)

(Of course, this solution applies, ony if you are a programmer and you can change the code....In other cases, the solution --as mentioned in previous messages-- is "OPEN the PDF externally, not in browser...by launching the viewer app.like Adobe reader..")

I think this is due to a registry issue.

On a VM, I did the following test:

- install 10.1, test : FAILED

- backup registry A

- uninstall 10.1

- install 9 and do update : SUCCESS

- backup registry B

- install 10.1 : SUCCESS

- backup registry C

- restore  backup registry A : FAILED

- restore backup registry C : SUCCESS

I did the last 2 steps twice.

If anyone is interested to see the diff3 files, I will keep them for a couple of days.

Bertrand