Skip to main content
J
jonathonr21308024
Known Participant
November 1, 2019
Answered

Embedded PDF viewing generates error 0:521 and crashes Internet Explorer

  • November 1, 2019
  • 2 replies
  • 15282 views

Hello,

 

We have at least 3 users that are affected by the issue in the Subject line. All machines are running Windows 10 Enterprise 64-bit with version 19.021.20047 of Adobe Acrobat Reader DC. I've also attached a screenshot of the error message users are receiving. It should be noted that this issue only began occurring after our environment was updated to this version of Reader DC; previous versions did not cause this issue. Is this a new issue in this build? Please advise.

 

Thanks.

    This topic has been closed for replies.
    Correct answer Eitan276256556llz

    I know it is old question, but I got the issue still with new version 2022 and I think I have identified the cause - at least in my situation.

    In Preferences -> Security (Enhanced) -> "Run in AppContainer" <- remove the tick
    Do it under considaration as it will reduce the protection offered by ACROBAT (as far as I can understand).
    Hope it will help out ...
    Cheers
    Ethan

    2 replies

    E
    Eitan276256556llzCorrect answer
    Participant
    December 19, 2022

    I know it is old question, but I got the issue still with new version 2022 and I think I have identified the cause - at least in my situation.

    In Preferences -> Security (Enhanced) -> "Run in AppContainer" <- remove the tick
    Do it under considaration as it will reduce the protection offered by ACROBAT (as far as I can understand).
    Hope it will help out ...
    Cheers
    Ethan

      E
      Eloualid27828845v0zs
      Participant
      January 10, 2023

      I tried to follow your instructions and they didn't work, I also did a repair and it didn't work and then I deleted adobe and reinstalled it but I can't solve the problem yet, can anyone help me? 

        A
        abagail.d.
        Participant
        January 31, 2023

        Hi
        Maybe try to:

        disable the "Enable Protected mode at startup"
        Disable "Enable enhanced security"

        (those options depends on the version of Acrobat you are on - i am on 22.003....)

         

        The issue as I understand it is, that Adobe Reader is not getting the file data fast enough to process for disply.

        Assuming the PDF is not embeded in another app, try to download it first. If it is the type that each "control click", load another page "on the fly" - it might be the PDF render on the backend too slow.

         

        Do it under considaration as it will reduce the protection offered by ACROBAT (as far as I can understand).
        Hope it will help out ...

        Ethan

        (my background is from the SAP world, so I am just guessing what is your scenario)

         


        I am having this issue with error code 0:521, I tried all fixes discussed, I went into CC and ran an update, and suprisingly there were updates available, Ive attached image. User is also having the issue when closing one pdf and opening another right away. Installed vertsion 22.003.20314. Swapped her pc to see if it is user or device issue, and she got the error on the new pc as well. I am hoping the update clears this up. We pay for this service. 

        Amal.
        Community Manager
        Amal.Community Manager
        Community Manager
        November 1, 2019

        Hi Jonathonr

         

        Thanks for reaching out. As described above, you are getting the error 0:521, correct?

         

        We see that you are using the version 19.21.20047. A new update for Adobe Acrobat/Reader DC got released on 24th Oct 2019 version 19.21.20049. Please update the application to the new version available. Go to Help > Check for Updates.

         

        For detailed information please refer to the help article https://www.adobe.com/devnet-docs/acrobatetk/tools/ReleaseNotesDC/index.html

         

        Let us know how it goes.

         

        Regards

        Amal

         

          J
          jonathonr21308024Author
          Known Participant
          November 4, 2019

          I just updated the affected machines to v19.21.20049. I will let you know what comes up if anything.

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