Persistent error in PDFE

[puckman]

Hello,
I've owned a licensed copy of PDFE for over 10 years.  I often get a repeatedly severe exception error which shuts down PDFE multiple time per boot-time session.  So I resolve it by re-booting my machine.

I tried to resolve it on my own through googling but to no avail.

I'll attach an image of the error notice I captured.  Hope you can help me out with this one.

Also, I also receive a lot of DDE errors for viewing the file after filtering and correcting.  However, didn't capture this one.  Just wondering if they're related.

Cheers

[RTT]

Instead of using the Acrobat plugin as the PDFE PDF reader try using the Sumatra PDF one, with the help of the NPAPI interface.
Sumatra PDF stopped delivering the NPAPI plugin with the 3.0 release, so you need to install the old 2.5.2 version (https://www.sumatrapdfreader.org/download-prev), to get the npPDFViewer.dll file. Make sure you select, from the SumatraPDF installer options, the "install browser plugin..." option. You can then install the latest Sumatra PDF over that one. The dll will remain and will still work with the latest versions, even the 64-bit ones.
After you configure PDFE to use it (check attached screenshot) you will have a much more stable reader, without these errors.

[puckman]

Would the Acrobat plug in also cause the following error?:

Code: [Select]

Access violation at address 004701D4 in module 'PDFExplorer.exe'. Read of address 00000004.

Exception class: EAccessViolation
Exception address: 004701D4
--------------------------------------------------------------------------------
Stack list, generated 21-10-2024 22:48:54
[004701D4]
[00404EA3]
[004704FF]
[0046CAB9]
[0046EA2A]
[00485778]
[00404BFF]
[00485778]
[0048883F]
[0046C3ED]
[007B66BB]
[004884BC]
[00437EB8]
[004735BC]
[00472A8B]
[00472B7E]
[00472DAE]
[009491E1]
--------------------------------------------------------------------------------
System   :  Workstation, Version: 6.2, Build: 23F0, ""
Processor: AMD, AMD Ryzen 7 1700 Eight-Core Processor          , 2990 MHz MMX
Display  : 2560x1440 pixels, 32 bpp
--------------------------------------------------------------------------------
(I deleted from the debug report the list of loaded modules deleted due to website's 20 000 character limit)
[center].[/center]
[center].[/center]
[center].[/center]

Active Controls hierarchy:
TPDEStringGrid "QEFTusjohHsje2"
TPanel "Qbofm7"
TPanel "Qbofm5"
TPanel "NbjoFmfnfoutQbofm"
TTabSheet "JogpQbhf"
TPageControl "TfmfduQbhf"
TScrollBox "NbtufsTdspmm"
TOSSCKDSC "QEG`Jogp"
--------------------------------------------------------------------------------



[RTT]

Doesn't seems related.
Can you consistently make (what steps) this error to show up?
Do you have a multi-display system?

[puckman]

I don't recall anything specific that I did to recall the error.  I was simply using it different ways such as an InfoEdit modification, or filtering and selecting a and the error would show up on rare occasion.

I haven't had time to follow up on your initial reply.  I will do this sometime this weekend, monitor it and let you know.

Thanks for your help. 

[puckman]

Doesn't seems related.
Can you consistently make (what steps) this error to show up?
Do you have a multi-display system?

I do.  BTW... eventually I installed the Sumatra viewe and am using it as the default viewer within PDFE.  I will monitor and report back.

Thanks for your help.

[puckman]

Instead of using the Acrobat plugin as the PDFE PDF reader try using the Sumatra PDF one, with the help of the NPAPI interface.
Sumatra PDF stopped delivering the NPAPI plugin with the 3.0 release, so you need to install the old 2.5.2 version (https://www.sumatrapdfreader.org/download-prev), to get the npPDFViewer.dll file. Make sure you select, from the SumatraPDF installer options, the "install browser plugin..." option. You can then install the latest Sumatra PDF over that one. The dll will remain and will still work with the latest versions, even the 64-bit ones.
After you configure PDFE to use it (check attached screenshot) you will have a much more stable reader, without these errors.

Switching the plug-in worked like a charm.