Skip to main content
S
shamsundarv54008661
Participant
October 18, 2021
Question

developer help - How to ReaderEnable the 64 bit Acrobat Reader Pro plugin

  • October 18, 2021
  • 3 replies
  • 1381 views

Compiled the BasicPlugin sample in AdobeAcrobat 64 bit SDK

The Plugin loads and after few seconds The Reader crashes.

1) How do we get the process of ReaderEnabling done ?

2) Where do we get the certificates verified by Adobe ?

3) If we want support and open a ticket with Adobe where do we email.

    This topic has been closed for replies.

    3 replies

    S
    shamsundarv54008661Author
    Participant
    October 22, 2021

    >>Does the same plug-in run successfully in Acrobat Pro without crashing? 

    The plugin works in 64-bit Acrobat Pro.

    But in 64-bit Acrobat Reader, the plugin loads and after sometime 64bit Acrobat Reader crashes.

    Giving the crash call stack below.

    >>Or does it also crash? With or without signing?

    I am using the certificate to sign. The certificates were procured a decade ago, and our plugin work very well with 32bit Acrobat Reader using the Win32 signing tool.

     

    For 64bit I used the new signing tool from SDK from here

    ..\Acrobat DC SDK\Version 1\PluginSupport\Tools\Reader-enabling Tools\win64

    The 64bit Acrobat crash call stack  

    [2021/10/12 11:57:30.663] enter Adobe idle...
    'Acrobat.exe' (Win32): Loaded 'C:\Program Files\Adobe\Acrobat DC\Acrobat\sqlite.dll'.
    Exception thrown at 0x00007FFA09444F99 in Acrobat.exe: Microsoft C++ exception: CInterruptedExeception at memory location 0x000000190A9AE718.
    'Acrobat.exe' (Win32): Loaded 'C:\Windows\System32\cryptnet.dll'.
    'Acrobat.exe' (Win32): Loaded 'C:\Windows\System32\gpapi.dll'.
    The thread 0x7fd8 has exited with code 0 (0x0).
    Proxy object acquired for write by thread 25420.
    Thread 25420 releasing Proxy object acquired for write.
    Proxy object acquired for read by thread 15068.
    Thread 15068 releasing Proxy object acquired for read.
    The thread 0x634c has exited with code 0 (0x0).
    Proxy object acquired for read by thread 15068.
    Thread 15068 releasing Proxy object acquired for read.
    Exception thrown at 0x00007FFA09444F99 in Acrobat.exe: Microsoft C++ exception: RNAException at memory location 0x000000190A9AE5C0.
    Proxy object acquired for read by thread 15068.
    Thread 15068 releasing Proxy object acquired for read.
    Exception thrown at 0x00007FFA09444F99 in Acrobat.exe: Microsoft C++ exception: RNAException at memory location 0x000000190A9AE290.
    Proxy object acquired for read by thread 15068.
    Thread 15068 releasing Proxy object acquired for read.
    Exception thrown at 0x00007FFA09444F99 in Acrobat.exe: Microsoft C++ exception: RNAException at memory location 0x000000190A9AE030.
    Proxy object acquired for read by thread 15068.
    Thread 15068 releasing Proxy object acquired for read.
    Proxy object acquired for read by thread 15068.
    [2021/10/12 11:57:32.033] enter Adobe idle...
    Exception thrown at 0x00007FF9FE7A1603 (vcruntime140.dll) in Acrobat.exe: 0xC0000005: Access violation writing location 0x000001DCD7260000.
    Unhandled exception at 0x00007FF9FE7A1603 (vcruntime140.dll) in Acrobat.exe: 0xC0000005: Access violation writing location 0x000001DCD7260000.

    The program '[0x4B50] Acrobat.exe' has exited with code 0 (0x0).

     

    S
    shamsundarv54008661Author
    Participant
    October 26, 2021

    The crash remains unsolved even with signed and Reader Enabled plugin.

    The crash happens as per the call stack listed previously, in Adobe 64bit Reader with Plugin.

     

    Bernd Alheit
    Community Expert
    Bernd AlheitCommunity Expert
    Community Expert
    October 19, 2021

    Read this:

    https://opensource.adobe.com/dc-acrobat-sdk-docs/devnet/rikla.html 

    R
    rrrowell
    Participant
    October 20, 2021

    Even after attaining a certificate and signing using the sign utility, my "hello world" application still crashes.  Using debugger, I can confirm that the PluginInit() function is being called.   Using procmon I can see that the crash happens after using some encryption service.  

     

    My "hello world" application is essentially just the "Starter" application from the samples, compiled in 64-bit mode.

     

    When signing the api, the utility got no errors and added around 500 bytes to the api file.  

     

    Is there a common pitfall that others have figured out?  

    T
    Test Screen Name
    Legend
    October 20, 2021

    Does the same plug-in run successfully in Acrobat Pro without crashing? 

    Or does it also crash? With or without signing?

    Peru Bob
    Community Expert
    Peru BobCommunity Expert
    Community Expert
    October 18, 2021

    I've moved this from the Using the Community forum (which is the forum for issues using the forums) to the Acrobat SDK forum so that proper help can be offered.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices