Skip to main content
MatthewMN1
MatthewMN1
Participant
November 29, 2017
Answered

Acrobat Reader DC "There was an error opening this document. Failed to load an application resource (internal error)."

  • November 29, 2017
  • 4 replies
  • 23796 views

Currently experiencing an issue with Adobe Acrobat Reader DC (18.009.20044) and Adobe Acrobat DC (218.009.20044). 

When opening documents that have been digitally signed or have a digital signature block, both will open but with the below error:

"There was an error opening this document. Failed to load an application resource (internal error)"

In order to view the document I have to click "OK" to close the error then reopen the same document again.

Working on Windows 10.

I've already tried the Repair Adobe tool, also this is affecting way more then just my machine.

Been on the Google for a good bit, but not finding anything relevant.  Any assistance greatly appreciated.

This topic has been closed for replies.
Correct answer mg_0316

Hi all,

We wouldn't recommend disabling what ereadslc has mentioned above in response no# 6.

Rather I would suggest/recommend try whitelisting the location/path under Security(enhanced) Preference for Reader/Acrobat.  Let us know if that helps.

-Tariq Dar


Tariq,

This is the solution we ended up going with to help keep this error from popping up.  Basically just define whitelisted locations in registry using group policy and everyone will have them.  I added whitelisted locations here in User Policy:

HKCU:\SOFTWARE\Adobe\Adobe Acrobat\DC\TrustManager\cTrustedFolders

HKCU:\SOFTWARE\Adobe\Adobe Acrobat\DC\TrustManager\cTrustedSites

I had to add strings in each key underneath both of those keys named t(whatever number you like) and put the value of the site or path.

Thanks for replying!

-Mike

4 replies

E
ereadslc
Participant
January 3, 2018

We have solved this issue by changing some registry keys.  For our purposed we needed to change the following registry keys to the settings below.

  1. "HKLM\SOFTWARE\Policies\Adobe\Adobe Acrobat\DC\FeatureLockDown   -     iProtectedView” to “1”.
  2. “HKLM\SOFTWARE\Policies\Adobe\Adobe Acrobat\DC\FeatureLockDown   -     iFileAttachmentPerms” to “2”.
  3. “HKU\.DEFAULT\Software\Adobe\Adobe Acrobat\DC\AVGeneral   -     bFIPSMode” to “0”

Specifically this key seems to be the main problem:

  1. HKLM\SOFTWARE\Policies\Adobe\Adobe Acrobat\DC\FeatureLockDown   -     iProtectedView” to “1”
C
Col_Mark
Participant
January 8, 2018

Even though those registry changes make the program work you are disabling the security.

iProtectedView to “1”

0=Off

1=files from potentially unsafe location

2=All files

Is there a way to verify the digital data,  When opening the PDF reader tries to authenticate the signatures (for Example) and install the certs automatically but fails.  If you open reader and then open the PDF the signatures work with out acknowledgment.  Is there a way to make this work by double clicking the PDF? Can we use Directory Servers to authenticate per system?

E
ereadslc
Participant
December 13, 2017

We are seeing this same issue on version 18.009.20050.  Several thousand installs all with the exact same result.  Our users are not happy and we have no solution yet.

cadbury
Adobe Employee
cadbury
Adobe Employee
December 5, 2017

Hi matthew,

Thank you for reporting the issue. Please go to Help -- check for updates , and update to the latest version.

Is this problem not observed on Windows 10? What are the platforms on which you are see the issue

If the problem is still resolved, please let us know, if this is happening for any particular file or for all the files.

Please try creating a signature with the latest Acrobat version and opening it with the same.

We cannot reproduce the issue in house. Also, you could share the file incase the document doesn't contain any confidential information.

Thanks ,

Chandrima

MatthewMN1
MatthewMN1Author
Participant
December 12, 2017

We're on Windows 10.

There seems to be no issues Opening PDF’s created on the current version of Acrobat, though this is not an option for the amount of Documents used.

All Docs here have this issue (The ones with Signature Blocks);

http://www.apd.army.mil/ProductMaps/PubForm/DAForm.aspx

J
johnb63679870
Participant
November 30, 2017

I've fixed this problem by adding common folder paths as Privileged Locations under Edit, Preferences, Security (Enhanced).  I still get the error message when someone sends me a PDF file, but most of my work involves getting digital signatures on files stored on just a few server locations.  I hope this helps!

MatthewMN1
MatthewMN1Author
Participant
December 4, 2017

Sadly this solution does not work for us, I appreciate the tip though. Still looking for a resolution to this issue.

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