Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
0

Acrobat Reader Control Crash

Guest
Jan 03, 2018 Jan 03, 2018

Copy link to clipboard

Copied

Hi All,

I'm having issues with the Adobe Acrobat Reader Control crashing when embedded in one of our apps. The users are rapid fire creating interactions, attaching a PDF, adding a bit of data to the interaction and firing that into their system. Every time a new interaction is done a new instance of the control is created.

After a indeterminable period of time (sometimes 20, sometimes 40, sometimes 80 times) their app will display a crash from Adobe (Window titled Adobe PDF Document) saying;

"There is a problem with Adobe Acrobat/Reader.

If it is running, please exit and try again. (10:10)"

We have no idea what is causing this error message, there's nothing in the application logs for this, and nothing in the windows event logs. Can Acrobat be configured to log to a file, or to an event log somewhere?

It's worth also noting that the user just needs to close and re-open the application and they can work normally again. The application is being delivered via Citrix also (7.14).

We are running Adobe Reader DC 2017.012.20093. Sandbox protections are off, but Enhanced security mode is on. We have disabled ia32.api in the plugins folder as we found this had caused issues due to not having any internet access from these systems.

I'm a bit at my wits end in figuring out what might be causing this issue, and it's being a real pain for the customer also! Any help would be appreciated.


Thanks,

Alex.

Views

862
Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jun 12, 2018 Jun 12, 2018

Copy link to clipboard

Copied

LATEST

This question should still be OPEN, not "Assumed Answered" as this issue still exists in Adobe Acrobat 2018.011.20035 and there is no mentioning of this being solved in build 20038 or 20040.

Votes

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines