Reader enabling Adobe plugins

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

Mmmm.. I'm not very sure. But I dropped a mail at the following address: [email protected]
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

Similar Messages

  • Reader enabling my plugin

    Hi all,
    Here is where I am at:
    I ran the MakeKeys and submitted the key to Adobe via the RIKLA form and was sent back the RIKLA-DigCert.rc file
    I have a compiled Adobe Reader Plugin with the "READER_PLUGIN" HFT preprocessor definition which works exactly as intended in Adobe Acrobat Standard.
    I have run SignPlugin with the following parameters:
    SignPlugin -kp keypair -cf RIKLA-DigCert.rc TT.api - with the result:
    "TT.api successfully Reader-Enabled""keypair" is the original keypair created by MakeKeys in the "kp" paramter
    I have done none of the "API_DIGITAL_CERTIFICATE" stuff, as found in the ReaderEnabling.pdf that is widely available - I assume this is very out of date for Reader X
    However, having done this, when I copy the TT.api plugin to the plugin directory of my or any other computer's Reader directory under Program Files, it does not load.
    Question is two fold:
    Have I missed a step? Perhaps something to do with API_DIGITAL_CERTIFICATE or something I need to incorporate into the VS2008 project...?
    How can I debug what is happening to prevent loading?
    I am happy to put up code or the actual .api file if they are useful,
    Thanks in advance for any advice,
    Dom

    I received a very helpful message from an Adobe employee who gave me the following information:
    [...] Is your plug-in based on any of the samples in the Acrobat SDK? If so, it will link to the AcroDspOptions.rsp file in the Samples directory in the SDK. You need to open this file in a text editor and remove the line:   /D PI_ACROCOLOR_VERSION=0x00060000        Save the file, then rebuild your plug-in and enable it with the SignPlugin tool. Note that some of the other samples in the SDK require this to be defined so you may want to copy it to another file so you can easily put it back later. [...]
    My plugin was based on the samples in the SDK, and removing this line from the AcroDspOptions.rsp file solved the problem.

  • Plugin issue after using SignPlugin and Reader-enabling

    Hi all,
    I would like to ask for a help with plugin that we have developed for Adobe Reader.
    We are running into an issue with the plug-in and I was hoping that you can help me out.  It looks like plug-in works perfectly in the Acrobat but we have an issue with getting it  to work with Reader as described below.  I would greatly appreciate your help.
    We have a problem with plugin after signing it using RIKLA certificate provided by Adobe and Reader-enabling.
    Our plugin has been developed to allow users to sign PDF XML data from Reader user interface using custom library (sign library) and msxml3.dll library ( to transform PDF form XML into custom XML format). Plugin target is Adobe Reader 9 and it has been tested using Adobe Acrobat 9 earlier. Recently we received RIKLA certification key and after we tried to sign plugin and use it in Reader we started to have problems.
    Plug-in, compiled directly from source code and installed in Adobe Acrobat 9 is working correctly. We haven’t experienced any issues and everything seems to be working properly.
    The same plug-in signed using SignPlugin tools from Acrobat SDK 9.1 (command SignPlugin -kp keypairFileName -cf Reader_Integrated_Key_FileName  MyPlugin.api) and RIKLA key is not working correctly in Adobe Reader 9.
    The problem appears when plugin is trying to access external library msxml3.dll and execute createProcessor() function.  The same function work properly in Adobe Acrobat 9 before sing plug-in with RIKLA key.
    Below there is fragment with code that doesn’t work in Adobe Reader after reader-enabling but works in Adobe Acrobat.
    Plug-in crushes in line pProcessor = pTemplate->createProcessor();.
    try{
      pProcessor = pTemplate->createProcessor();
    } catch(_com_error &e) {
      printf("Error setting XSL style sheet : %s\n",
             (const char*)_bstr_t(e.Description()));
      AVAlertNote("Error setting XSL style sheet");
      AVAlertNote(e.Description());
      exit(-1);
    Code that we use in catch() block lets us know that error source is “msxml3.dll” library.
    As we have discovered problem occurs only after Reader-enabling .api plugin file. Clear compiled .api file works properly in Adobe Acrobat 9 without any problems.
    We would like to know if you have experienced any similar issues? If yes, what have caused them?
    Why same plugin is working in Acrobat 9 before signing and after signing using provided certificate it stops working?
    Are there any restrictions of using external libraries in Reader that are not working there, and these restrictions are not obeyed in Acrobat?
    Any help would be greatly appreciated.

    Hi Irosent,
    Is there a way that Acrobat and Reader differentiate between library initialization?
    Would it be useful if I place any part of code or project configuration for you so maybe you will be able to help?
    Libraries that we use (our own dll files) we place in windows/system32 folder (there also exists msxml3.dll file that we use).
    Here are preprocessor definitions that we have defined:
    _AFXDLL
    _USERDLL
    READER_PLUGIN
    NDEBUG
    WIN_PLATFORM
    WIN32
    _WINDOWS
    WIN_ENV
    ACRO_SDK_LEVEL=0x00090000
    As for library msxml3.dll that we use in code we have:
    #import <msxml3.dll>  named_guids
    using namespace MSXML2;
      MSXML2::IXMLDOMDocumentPtr
              pXml(MSXML2::CLSID_DOMDocument);
      MSXML2::IXMLDOMDocumentPtr
              pXslt(CLSID_FreeThreadedDOMDocument);
      IXSLTemplatePtr pTemplate(CLSID_XSLTemplate);
      IXSLProcessorPtr pProcessor;
    Later there is a part of code that I have posted in first post and where plugin crashes.
    I would really appreciate your help.

  • Saving via Reader-Enabled plugins - An unimplemented or obsolete function was called

    Hello,
    I have recently Reader-Enabled my plugin, and am getting an issue using PDDocSave; getting "An unimplemented or obsolete function was called".
    Testing in X and XI has the same response.
    Reading Re: Acrobat Reader X and PDDocSave it seems that it is a bug in X, but I would have assumed something like this would be fixed by XI.
    The below code has it saving the file where it is, but I am also calling the function with the PDSaveCopy flag to a different location and get the same result.
    AVDoc avDoc = AVAppGetActiveDoc();
    PDDoc pdDoc = AVDocGetPDDoc(avDoc);
    ASFile asFile = PDDocGetFile(pdDoc);
    ASFileSys asFileSys = ASFileGetFileSys(asFile);
    ASPathName asPath = ASFileAcquirePathName(asFile);
    PDDocSave(pdDoc, PDSaveFull | PDSaveLinearized | PDSaveCollectGarbage, asPath, asFileSys, NULL, NULL);
    I thought perhaps the save flags may have been the issue, but eliminating one-by-one had no change.
    I don’t have the /READER_PLUGIN conditional on, if I do I cannot compile at all - Re: How can I save current document in my Reader plugin? 
    Thanks for your help. Thought I'd ask here before putting in a support request.

    One thing I notice in the docs for PDDocSave:
    IMPLEMENTATION LIMIT: the current implementation can
    only save a file to the same fileSys for the doc's current backing
    file, thus fileSys MUST BE NULL, otherwise the error XXX is raised.
    This is also reiterated in the other headers:
    @param fileSys The file system. If it is NULL, uses the fileSys
    of the document's current backing file. Files can only be
    saved to the same file system. fileSys must be either NULL
    or the default file system obtained with ASGetDefaultFileSys(),
    otherwise an error is raised.

  • Enable Adobe Reader to Digitally Sign PDF created with Acrobat Pro 9

    Hi All,
    I am trying to figure out how to enable adobe readers to digitally sign PDFs I create. I currently have Acrobat Pro 9.
    Customer Support said that I need to save it as a "Reader Extended" format, but I cant find this option anywhere.
    Any help would be appreciated.
    Thanks
    Matt

    Thanks Ben,
    Unfortunately, that video is for acrobat X or above and I cant find the "save as reader extended" option in Acrobat Pro 9.
    Can this be done from this version?
    Thanks again
    Matt

  • Adding attachments to Reader enabled forms in Adobe reader

    I am creating a form for a user where they need to add an attachment to the form from Adobe Reader.
    They also need to save the form locally, as this is a low volume usage, approx. 100 uses in total the rights are being enabled in Acrobat Professional 8.0
    Functionality all works fine until the form is reader enabled and the script no longer functions.
    the script being used is as follows
    var oDoc = event.target;
    oDoc.importDataObject("Strategic Research Plan");
    var d = oDoc.getDataObject("Strategic Research Plan");
    app.alert("The name of the file you attached is: " + d.path);
    I have seen some comments indicating the file system cannot be accessed when rights have been applied, does anyone know if this is the case? or if there is a way to make this work.
    this is being done with Professional 8 and Reader 7.02 or later
    Any comments will be appreciated!

    Hi Pat,
    Yes I was using Firefox 19 indeed. This certainly fixed it.
    Thanks for the help!

  • Adobe Reader Digital Signature Plugin

    Hello All,
    We had developed a adobe plugin for digital signature through smart card. The plugin works fine for Adobe Professional. I would like to know the procedure how to make it work for Adobe Reader. I found a URL http://www.adobe.com/devnet/reader/ikla.html which says to buy a license. I'm confused over DRM and non-DRM agreement.
    To make it clear, our company shall be distributing the smart card and the plugin in the enterprise market for digital signatures that need to work with both Adobe Professional and Adobe Reader. Our customers shall be probably using Adobe reader.
    Can any one let me know the procedure to make reader plugin?
    Regards,
    Madhukar

    Hi Gatis,
    Check out the Security and Digital Signature Admin Guide athttp://learn.adobe.com/wiki/download/attachments/52658564/acrobat_reader_security_9x.pdf?v ersion=1
    http://learn.adobe.com/wiki/download/attachments/52658564/acrobat_reader_security_9x.pdf?v ersion=1
    Once you get the file open look at section 5.3.4.4
    The folder path has to exist, but Acrobat will create the file if it's missing. For example, if you want to save the file to C:\LogFile\digSigLog.txt the folder LogFile would have to exist on the C drive, but the log file itself will get created if it's not there already.
    When you type in the file path and name in the Edit Binary Value dialog in regedit, make sure you null terminate the string by typing a zero at the end of the hex data on the left side of the dialog. It will look like a dot on the right side, but it's not really a dot (a dot is 2E in hex).
    Steve

  • Reader enabling plug-in on Mac OS X

    Hi,
    I have successfully created and reader-enabled a plug-in on a Windows platform (prooving that the KeyPair and certificate I have are correct).
    The same plug-in works fine too with Acrobat on Mac OS X.
    But I could not manage to reader-enable it on Mac OS.
    In the Release notes / Issues for Acrobat XI SDK, I've found this :
    MakeKey Reader-enabling Tool
    At this time, the MakeKey tool for Reader-enabling does not generate keys if you are using Mac OS 10.x on MacIntel or Windows Vista on 64-bit machines. Please check www.adobe.com/go/acrobat_developer periodically for future updates to this tool.
    And in the Tools folder for mac in the SDK in empty... I've tried with similar tools provided with 9.1 SDK but... even it SignPlugin says the plugin has successfully been enabled... it does not load...
    So... How is it possible toe reader-enable a plug-in for MacOS X ?
    TIA,
    J.

    Problem solved by upgrading to Java 7

  • Need clarification on "reader enabled" in LC ES

    Is "reader enabled" some plug-in or just an option to "mark" before I start developing new form? Cant find much about it in LC help but I see its very important for later user-end capabilities (like sending filled pdf by e-mail using only adobe reader...). If its a plugin, is it needed only on developer station or every user of that form?
    Please advice.

    Niall O'Donovan wrote:
    (1) is using Acrobat Standard (v9) or Acrobat Professional (v8 or lower). In Acrobat v9 under the Advanced menu is an option to enable the form. Click this and save the form with a different name. There are license restrictions when you use Acrobat.
    This is weird, I use Adobe Acrobat 9 Pro (9.0.0) and there is no such thing as "reader enabled" in my advanced. I checked whole tree and cant really see anything equivalent to this.
    There is "Change reading options" but its diabled (cant be used) with or without my form loaded.
    If you could be so kind and elaborate especially on this what is mentioned in last columnt of this screen.
    Its only possible to do so if we had
    (2) Adobe have a server component to their LC Enterprise Suite called LC
    Reader Extension ES2. This is intended for enabling large numbers of
    forms and/or for large numbers of recipients. This is an expensive
    option because it is server based and intended for large organisations
    or government agencies.
    Thank you very much for your insight. Best regards.

  • Can't Enable Adobe

    Just upgraded my Adobe plugin in Mozilla, but now can't enable it - can anyone help? Thx

    After recently rebooting, now shows my current version of Adobe Acrobat is 11.0.2.0.  But whenever I try to view a file, like youtube, system tells me my "plugin is vulnerable and needs to be updated".  When I view my Mozilla status for plugins, it tells me that that version (updated in Feb 2013) is okay.  What's going on??  Where do I go now to fix this??  I'm not a real computer buff.....

  • When I try to save a form as "Reader Extended PDF" in Acrobat Pro, I get an error message "This document could not be reader enabled".

    Hello,
    When I try to save a form as “Reader Extended PDF” in Acrobat Pro, I get an error message “This document could not be reader enabled”.
    The steps I’m following are described below:
    1.    Insert electronic signatures
    - In Tasks, click on “Add New Field -> Digital Signature”.
    - Move the square to the place where you want to put the signature and click.
    - Fill in the “field name” with the name of the person who has to sign here.
    - When it is done, click anywhere on the screen.
    - In Tasks, click on “Close Form editing”.
    - Go to menu “File -> Save as -> Reader Extended PDF ->Enable additional features”, click on “Save now”.
    - Fill in the file name and click on “Save”.
    2.    Save the Form
    - In Tasks, click on “Close Form editing”.
    - Go to menu “File -> Save as -> Reader Extended PDF ->Enable additional features”, click on “Save now”.
    - Fill in the file name and click on “Save”.
    I am using Adobe Acrobat Pro 10.0.0 on a W7 workstation
    Here's a screenshot of the problem.
    Thanks a lot.
    Gael

    Read the user manual that came w/the scanner and/or contact HP Support.
    http://support.apple.com/kb/PH14141 OS X Mavericks: Reset the printing system 
    http://support.apple.com/kb/HT3669 Printer and scanner software available for download 
    A scanner driver you may wish to consider:  VueScan Scanner Software

  • Unable to submit a Reader-enabled PDF: "This operation is not permitted"

    Hi I've looked through the forums but haven't found an answer to this particular query: I've created a simple form (text boxes, radio buttons, and a submit button which should send the entire PDF to an email address). I have tried different options:
    Reader enabled the form, then saved it and emailed a copy to a friend to test. When he clicked on "submit" he received the error "this operation is not permitted". Unfortunately I didn't ask what version of Reader he has. The form was created in Adobe Acrobat X.
    Did not reader-enable the form, but opened it with Adobe Reader XI. When I click on submit I get a "server connection error". I'm using Gmail, Chrome and Windows 7 (I went to Start > Default Programs and was able to associate "MAILTO" with Chrome, but there is no option to actively choose Gmail as my mail client). p.s. Before submitting the form I checked and my internet connection is up and running.
    I tried to submit the form from Acrobat X and I get a similar error, "Acrobat is unable to connect to your email program".
    There are no unembedded fonts or hidden objects in the PDF.
    Any help would be greatly appreciated!
    Melissa

    Submitting forms by email isn't really submitting. In my view it's a useful quick test, but not suitable for production use. For reasons you've already discovered. A particularly bad case is where a user uses GMail (or whatever) but has a WORKING email client that accepts the mail; but then it goes nowhere because they never set it up.
    Submit really means "send to a web server" (where a script written by a professional will handle the data). Like the forms on every web site.
    Web sites COULD "submit by email" too, but they don't because it isn't any good.
    (Caveat: some big companies control the email set up exactly, and it can work for them.)

  • Reader enabled PDF won't save to Word

    Hi,
    I'm sorry if I'm not putting this question in the right place, but I can't find a better location.
    We have a PDF that's reader enabled for editing with the typewriter tool, and we want to save it as a Word document.  Whenever File > Save as >  Word doc is clicked, we get a message that Acrobat has stopped working.  This is only with this particular PDF, as we've tried 'plain' ones that converted beautifully.
    How can I save the reader-enabled PDF as a plain PDF?
    Thank you!

    Thanks for replying!
    There is no 'Save a copy' in the File menu; maybe that option is just in
    Acrobat, not Reader.  I solved it, though; what I did was print to Adobe
    PDF.  As we know, that doesn't actually print anything, it just saves; and
    it was saved as a plain PDF!  Well, that was a lesson learned...and enabled
    PDF cannot be converted.
    Thanks anyways!

  • FORMS: Reader Enabled forms are not saving for all users

    I have created several fillable forms with both Acrobat Pro 8 & 9. All have been created with Extend Reader Rights In my testing i have success saving the forms in Reader (various versions as old as 7).
    After sending the forms out via email the saving functionality is hit and miss for all of our employees. Some can save others cannot. I can't seem to find a common thread as to why this is happening.
    All forms are created on a Mac OS X 10.6.1 and then sent out via email to Windows and Mac users about 50/50. Both OS users are having trouble
    There is no need to collect the data on a server or anything just trying to make it easier and waste less paper. We don't mind send PDF attachments all the time.
    Any help would be great!
    Thanks!

    here is one of the forms that is not working in Reader (except on my wife's PC and another Mac) it is the current PDF form i am having trouble with. If we can resolve the issue then it will help me resolve my other forms too. I have made them all using the same process. (Maybe therein lies a problem)
    Form Creation Process:
    Create initial page layout in Pages (mac app for those that are not familiar)
    Export as PDF
    Open PDF in Acrobat Pro 9 (started making forms in v8 now i am working in v9 - both have produced this problem)
    Run Form wizard, adjust fields, save final version of form
    Extend Features in Adobe Reader (via Advanced menu) - Follow steps to save a new Reader Enabled version
    Email new RE version to co-workers
    All can fill out the form, only a couple can actually save the partially completed / fully completed form for reference, filing, or submission.
    Am I missing something? Thanks for all the help so far!

  • Script on parent pdf opens attached pdf, but attached is no longer Reader-enabled

    Hello everyone,
    I have a fill-in pdf that uses the following JS to auto open an attached pdf:
    this.exportDataObject({cName: "mypdf.pdf", nLaunch: 2});
    Now, the problem is that the user (if using Adobe Reader) cannot save data entered into the attached document.  Using Acrobat, I reader-enabled the attached file "mypdf" before attaching it to the parent pdf.  Somehow, when it becomes attached, it just loses this functionality.  Even when I reader-enable the parent pdf, it warns me that it cannot reader-enable attached files.
    This seems like a huge flaw, so I imagine there's a solution.  Any ideas? Anyone face this problem before?

    That's extremely helpful. Thanks. Works fine now. David

Maybe you are looking for