Reader enabling Adobe plugins

[Harsha...@adobeforums.com]

Hi,

I've been trying to Reader enable my plugin that works well with Acrobat Pro 9.0. However, everytime I load the plugin in Acrobat Reader 8.0, it throws an error saying "Invalid plugin detected. The reader quit"

I have ensured that "Certified plugins" flag is disabled in the Reader.

My guess is that either I'm not following the right steps for enabling the plugin or my key is corrupt.

Can anyone tell me the exact steps for reader enabling a plugin if I'm using VS .NET 2005? Are the steps any different from VS .NET 2003?

Also, is there a way for me to verify if the key I've received is corrupt?

-Harsha

[Leonard_...@adobeforums.com]

So you have received a key from Adobe then already? If so - excellent, that's the most important part..without that you can't continue.

If you have the key, are you following the instructions EXACTLY? They are the same steps as documented in the SDK - which will be for VS2005 in the Acrobat 9 SDK.

Be aware, however, that Reader keys are ONLY GOOD for the version they are licensed against. So if you have a Reader 9 key, it won't work in Reader 8. And related, if you built for Reader 8, you need VS2003 and not 2005.

[Harsha...@adobeforums.com]

Hi Leonard,

I went through the steps in Acrobat 9.0 SDK. It suggests using the SignPlugin tool for reader enabling plugins. When I followed the steps and ran the SignPlugin tool, it threw an error saying "Coud not write into the resource for the plugin"

I'm not sure why this is happening. The SDK documentation does not really provide any VS 2005 steps. It basically simply suggests using the SignPlugin tool after receiving the Encrypted key from Adobe.

I also tried using the steps in Acrobat 8.0 SDK documentation. This o ne suggests using the Makemd32.exe. But this was not helpful either. Any suggestions??

-Harsha

[Harsha...@adobeforums.com]

Hey,

Quick update: The error that I receive on running SignPlugin is "Can't update resource in plugin". Not sure what that means.

So basically, right now the steps in SDK 8.0 documentation are not working and the steps in SDK 9.0 don't work either.

Not sure if I'm doing something wrong or if the key is corrupt. Any thoughts on how I can move ahead?

-Harsha

[Leonard_...@adobeforums.com]

Right - in the 9 SDK we provide a new and improved tool for signing the plugin. You want to use that instead of the older method - but it also requires newer Reader 9 keys.

[Harsha...@adobeforums.com]

Hi Leonard,

The key that I've received is for Adobe 9.0 I beleive. The contract says that the key is valid for Adobe Reader 8.0 and 9.0. I also dropped a mail to the supprot guys at Adobe, who confirmed that the key will work with both versions. But I'm still getting the following error:

"Can't update resource in plugin"

-Harsha

[P...@adobeforums.com]

I also dropped a mail to the supprot guys at Adobe

Which 'support guys'? Did you contact Developer Support or Technical Support?

[Harsha...@adobeforums.com]

Mmmm.. I'm not very sure. But I dropped a mail at the following address: rikla-...@adobe.com

BTW, SignPlugin stopped throwing that error. It successfully "Reader Enables" my plugin. But the plugin does not load in Adobe Reader.

I read in the documentation that checking the size of the key helps you identify if its corrupt or not. The Integration Key that I received from Adobe is 129 bytes long. Could it be corrupt?

Also, to be more precise about the steps that I follow if I don't use SignPlugin (I basically tried both approaches. But neither of them worked):

1. I basically add Dummy.rc as a project resource
2. I then open the "API_Encrypted_DIGEST" Resource and paste the key that I received from Adobe below, the first 64 bytes of data (all 0's) that is already there.
3. I then buld the plugin
4. Then I used the Makemd32 tool to generate the actual Digest
5. Once that was done, I replaced the first 64 bytes with the data I received after running the tool
6. I then Build the plugin again (not Rebuild)
7. I then place the .api file in the plug_ins folder of the Reader

Am I doing something wrong here? Should I be having two resource files? One for the Encrypted Digest and one for the Digital Certificate. I have project deadline coming up and I'm completely clueless about what;s going wrong. Any guidance would be great!

-Harsha

[P...@adobeforums.com]

Open a case with Acrobat Developer Support - they'll be able to help you get your plug-in loaded in Reader.

<http://www.adobeforums.com/webx/.59b68c9a>

[Harsha...@adobeforums.com]

I'm not sure how to "open a case". Is there a fee involved?

[P...@adobeforums.com]

Did you read the link I posted? It contains a link to the Developer Support page which lists the phone number to call to open a case as well as the list of fees based on what you need.

[Harsha...@adobeforums.com]

I did read the post. The project is actually for a customer. And it would be great to have this done without asking them to pay additional fees, given that they've already invested in purchasing Adobe Professional and the Reader Key. As an outsourcing partner, it will be difficult for my company to justify why we need them to pay this additional fees.

Can you point me to a link where I could verify my steps or find out if my key is corrupt.

[P...@adobeforums.com]

Can you point me to a link where I could verify my steps or find out if
my key is corrupt.

Unfortunately, no. This is done through Acrobat Developer Support, which is why I directed you to them.

[Sanctus_...@adobeforums.com]

Try this Developer Document:
<http://support.adobe.com/devsup/devsup.nsf/docs/54319.htm>

Sanctus