Install the Secure Document Plugin for Adobe Acrobat Reader
Copy link to clipboard
Copied
I'm trying to view secure PDF files downloaded from an organization of which I'm member. My computer is registered with their site as I have linked my computer to my subsciption with their organization. Viewing PDF files downloaded from their site has worked fine for years until a couple of days ago.
Now when I go to open the secure PDF files my web browser automatically opens to this site:
http://plugin.fileopen.com/Default.aspx?bhcp=1
...which seems to be offering some bundle of plugins that I've downloaded four times now.
But the secure document still won't open.
I uninstalled my old Adobe Reader 9 and installed the latest Adobe Reader X1
I've tried to re-register my computer with the organization's site but it won't allow me to register.
A prompt appears saying:
The security plug-in required by this command is unavailable.
DRMRegistration.pdf
I'm using Mac OS X Version 10.6.8
Adobe Reader 11.0.0
Any help opening these secure documents would be greatly appreciated.
Thanks
Copy link to clipboard
Copied
You should contact the suppliers of the file, OR of the plug-in. Adobe don't have any control over this.
Many plug-ins do not work with Reader XI (and Acrobat XI) and new versions may be required.
In general, if you use ANY plug-in you should check for compatibility before you upgrade the software into which it plugs. This happens constantly.
Copy link to clipboard
Copied
Hi!
I am having the same exact problem! Same exact message and everything. Trumanwater were you ever able to get this to work? I have checked the download location for FileOpen and it's listed under plug-ins when I go into Adobe Reader via Finder; however, when I open Reader and go into "About Adobe Plug-Ins...", FileOpen is nowhere to be found and I continue to get the same message you are getting...I'm totally mystified! I'll be contacting my organization as well as FileOpen but figured I would ask you too!
Thank you!
Copy link to clipboard
Copied
Don't be mystified, there's a very good chance of this in any plug-in; always check plug-in compatibility before upgrading a product.

