Skip to main content
S
SQNAdministrator
Inspiring
May 16, 2019
Question

Build 19.012.20034 - Windows 10 - Error 0:521 - a work around

  • May 16, 2019
  • 2 replies
  • 28529 views

Hi

Adobe Acrobat build 19.012.20034
Windows 10

When navigating between multiple PDFs, error 0:521 "There is a problem with Adobe Acrobat Reader.  If it is running, please exist and try again" occurs if moving to the next PDF is delayed by more than 4 seconds.

The Windows 10 event log reported:

"The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} and APPID {15C20B67-12E7-4BB6-92BB-7AFF07997402} to the user XXXXXXXXXXXXX SID (XXXXXXXXXXXXXXX) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool."

These class ID's and App IDs are linked to the AppRuntimeBroker ...

Resolution:

  • In Edit > Preferences > Security (Enhanced)
  • Un-check "Run in AppContainer"
  • Restart Acrobat.

The setting 'Run in AppContainer' is on by default in the 19.012.20034 build.  It was off by default in the 2019.010.20099 build.

Andy

    This topic has been closed for replies.

    2 replies

    S
    Sokni5EA3
    Participant
    June 16, 2021

     

    AkanchhaS8194121
    AkanchhaS8194121
    Legend
    May 17, 2019

    Hi Andy,

    Thanks for sharing the detailed description.

    As mentioned, while navigating between multiple PDFs the error message appears "There is a problem with Adobe Acrobat Reader. If it is running, please exist and try again" , do you get this message only when navigating the PDFs within the application or while viewing them on web browser as well?

    Since you have already tried disabling the "Run in AppContainer" and it didn't give any help. For testing, you may try disabling the "Enable Protected Mode at startup" from the Sandbox Protections once.

    Note: Changing the above security settings could pose security risks. We suggest you to turn it back On once you are done with testing.

    Thanks,

    Akanchha

    A
    Anonymous
    July 10, 2019

    @Akki_24: got the same situation with about 500 users. Also happens with build 20035. the workaround does it. But where is the right solution right now?

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