10.1.2 Displays grey, blank page (Fixed with 10.1.3)

I am waiting to receive

not sure if it is applicable in the thread, but running reader 8.2 i was having the same issue.  I played around with preferences for a while and finally succeded to get the document to display by checking off "show large image" in <Preferences - Page Display - under panel labeled "Page Content and Information">

We were having this problem as well.  We have several sites that returned PDFs via HTTPS.  Many of our users were fine but those with XP would just get a blank page returned.  Our sites that return via plain HTTP were fine however.  One of our developers narrowed it down to the cache settings in the content header being different on HTTP vs. HTTPS.  The HTTP versions were getting cache settings of "Private" while the HTTPS versions were defaulting to "NoCache".

Fortunately, we already had a wapper service between our web sites and the SAS intrnet server that is generating the PDFs.  He added the following lines to that wrapper and it solved the problem.

Response.CachControl="Private"

Response.AddHeader "Pragma", "Private"

The "Pragma" if a MS specific header which might explain why this appears to only effect IE.

Hope that might point some of you in the right direction 

Tom_5696, I attempted to contact Citibank IT Tech support in Sydney and Citibank Queen Street Brisbane today (over the phone and in person, respectively) to try and discuss the circumstances of their issue and compare notes, IT Manager to IT Manager, but they politely advised they are not experiencing Adobe 10.1.2 and IE issues. I even showed them a copy of this forum posting, but it was dismissed. They did acknowledge issues with Safari and Adobe Reader.

Our 10.1.2 form loading issues occur intermittenly: sometimes everything works, other times the form gets stuck loading 107kb/0kb (or similar) and a grey screen. It happens in only our production environment, but not in our pre-production environment. Both use https. We've done system and application traces and had sent them to our vendor who are looking for a configuration issue.

The recent patch appears to resolve the issue, but I am still looking for confirmation elsewhere from an organisation such as Citibank. I am allowing our vendor to continue to trawl through the traces to try and determine why it does not happen elsewhere in our systems.

Hi All,

Try this hotfix and check after rebooting the machine:

http://kb2.adobe.com/cps/930/cpsid_93026.html

Regards,

Sandeep V.

Just received a patch from adobe below.  This worked for us.  Requested release date but no reply to date.

Hi,

Adobe has come out with a fix for the issue wherein the PDF is not being rendered properly when viewed through a browser, post updating to Reader 10.1.2. Since, the fix is in testing stages, could you please apply the same on a single system (Since, this for Testing Puposes only, do not deploy this across your network) and let me know if it fixes the issue at your end. You can download the EXE from: https://acrobat.com/#d=5c-aA12ca6hSO4TKZ4mbyQ

The steps to apply the fix are as below:

1. Log in to your computer as an Administrator.
2. Download the file using the above link.
3. Unzip the file to extract the executable AdobeAcrobatReaderPatch10.1.2_cpsid_93026.exe.
4. Do one of the following to run the application:

          a. Double-click the EXE file.

           b. Run the EXE file in silent mode by specifying the -silent flag on the command line. Open the command prompt ‘As Administrator’ to avoid UAC prompt dialog.

               Example: <path to exe> -silent

  5.  Once the process is completed, you receive a prompt stating the result of the operation. You can choose to restart the system (if prompted) at that momemt or later, but a restart would be needed to ensure that the fix has been applied correctly.

  6. A log is created in the temp directory (%temp%) with the name AcroPatchApplication1012.log.

Do let me know if this fixes your issue.

Thanks

Ankit

We are experiencing the same issue and it is very urgent for us. 

We have thousands of new remote customers going live this month who rely on this pdf view aspect of our service and we cannot insist on them using chrome or firefox. 

We have raised a case with Adobe support

Case #0182998569

No feedback from support to date, several follow-up calls, resisted Adobe's support staff attempts to lay this issue at IE 9's door. 

Very keen to test the patch if an Adobe employer share this with us?

Our own investigations also seem to point to headers (removing them gave us a solution that worked temporarily/for some users) and gzip are the probable cause but we have been unable to get to the bottom of it.

Good News: I have been PM'd by an Adobe person with a link to a downloadable English-only patch that hopefully fixes this issue. I have replied to say I haven't got time to re-install the newer Acrobat and try this fix for some time so it may be helpful if more people watching this thread make themselves known and thereby give Adobe the chance to offer this download to you, too.

I don't know quite why Adobe don't just post a link in this thread, but maybe they are concerned about it getting too much exposure too fast.

Either way, if you make yourselves known, you may get a PM and the option to try something that may fix your problem.

The more the merrier, I think.

Thanks to Adobe for responding ...he says, in advance of finding out if it works ;-)

Steve.

I have a client who is experiencing the same issue with their web application, which presents PDFs (sent over SSL, not gzipped) within the browser. Upon upgrading to 10.1.2, their users are seeing grey screens (like the one shown in caseattle's screenshot) instead of the PDF document. The bug occurs regardless of the document being printed.

I'm able to get things back up and running on 10.1.2 by adding a Content-Length header when sending the PDF.

They were also experiencing what seems to be an unrelated 10.1.2 bug - when attempting to print directly from the browser, Acrobat Reader was crashing. This can be worked around by turning off Protected Mode.

I'm shocked to hear that a fix has been developed but is being pushed to the next quarterly release. These are fairly significant issues for web application vendors, and advising clients to downgrade to an older and less secure version of Adobe Reader is certainly not a solution that inspires confidence in Adobe.

The issue was happening with ADP, Wells Fargo and US Bank.  Downloading the PDF to a file and opening worked just fine.  It was just the embedded Reader in IE that seemed to be affected.  Toggling compatibility mode also allowed the PDF to be viewed, but that is not a fix.

As to the idea that there is a small number of users affected, I think that Adobe is wrong on that one.  Many people do their homework first to see if there are any glaring issues, so many probably have held back on this.  Others may have installed it but don't use the embedded Reader.  Then there are others still who don't open PDF files from HTTPS / SSL websites.  I get that it has to be recompiled, but this version will NOT be widely used with this bug.  Fix it and the others that have been discovered and release it as 10.1.3 before the "quarterly" update as 10.1.2 is useless in many peoples eyes.

We are back on 10.1.1 until this issue is resolved.  Hopefully the security issues or other bugs don't bite us in the meantime while we wait.