These forums are now Read Only. If you have an Acrobat question, ask questions and get help from one of our experts.

Reader X in Browser Link Returns Blank Page

TechGuy
Registered: Feb 10 2011
Posts: 2

This symptom is a bit erratic with variations using manual install or Adobe Customization Wizard. The only way I've gotten Reader X to work realiably in the browser (overwriting Reader 9.4.2) is to uninstall both Acrobat Pro 9 and Reader, reinstall Reader X, Pro. Not good solution for 90 workstations.

My Product Information:
Reader, Windows
dthanna
ExpertTeam
Registered: Sep 28 2005
Posts: 248
Michael,

This is an area that could stand a little work with in the deployment arena. The problem is compounded by the overall general messiness of the browser plug-in architecture, and how browsers interact with Windows at a system level. In short, it's layer upon layer upon layer upon layer of cruft. And, the easiest way to clean up the cruft is to tear it back to the studs.

Follow the HKEY_CLASSES_ROOT registry keys for .pdf, Adobe.AcroIEToolbar, Adobe.AcroIEToolbarHelper, etc. to see what I mean. Some of them chain, upon chain, upon chain through the registry. At any point if the wires get crossed POOF! it doesn't work.

For example, Adobe.AcroIEToolBar points to AdobeAcroIEToolbar.1, which points to CLSID {47833539-D0C5-4125-9FA8-0819E2EAAC93}, which points to C:\Program Files\Common Files\Adobe\Acrobat\ActiveX\AcroIEFavClient.dll, back to the calling entries as well as off to {04C567CB-A52F-41f4-9628-10CC965E7179} which also points to C:\Program Files\Common Files\Adobe\Acrobat\ActiveX\AcroIEFavClient.dll

It's not necessarily Adobe Engineering's fault. The guy that develops the installer systems is a pretty smart cookie! Much of the decisions made have to do with the environment in which Adobe has to operate within.

Douglas Hanna is a member of the Production Print Technology team at Aon.
www.aonhewitt.com

TechGuy
Registered: Feb 10 2011
Posts: 2
Doug: Thanks for the response. The user whose reinstall was working under IE, stopped working after a few hours. So I imagine you have to remove any related dangling keys you referenced in the registry after the uninstall of Reader and and Pro. As you describe, the registry interactions *are* pretty convoluted and I *would* like some sort of solution from Adobe since the only probable solution at this point is to create a new updated workstation image and redeploy.
dthanna
ExpertTeam
Registered: Sep 28 2005
Posts: 248
Michael;

Our last-resort, end of the line, solution (just short of reimage) is uninstall Reader, Acrobat, etc. Reboot (still an important step as it's the only way to definitively release .dll's that may still be loaded. Run CCLEANER (www.ccleaner.com. It will take you to Prinform, that's OK) to scrub down the registry really good. Another reboot (final rinse) then start to reinstall and test one problematic app at a time.

For the browser stuff, I would check to make sure that there are no browser windows open (check Task Manager) before starting much of this. It can be a bit tedious, but can be done. I have some other posts floating out here on how to deep-dive scrub Acrobat off of a workstation. Search on those if necessary.

I hope this helps.. and good luck!

Douglas Hanna is a member of the Production Print Technology team at Aon.
www.aonhewitt.com