HTTP ERROR 503 Problem accessing /. Reason: AuthenticationSupport service missing. Cannot authenticate request. | Community
Skip to main content
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by vanegi

Hi @akshaybhujbale,

Please check the logs to verify the root cause. You may consider the following:

1. run a data store consistency check for potential corruption.

Fix Inconsistencies in the repository when SegmentNotFound Issue is reported in AEM 6.x

2. run index consistency check and potential corruption.

Use oak-run.jar to Manage Indexes

 

Thanks !

 

3 replies

ShaileshBassi
Community Advisor
ShaileshBassiCommunity Advisor
Community Advisor
July 13, 2022

@akshaybhujbale Please check that all OSGi bundles have the status “ACTIVE” in the OSGi console.  Start any bundles that do not have the “ACTIVE” status and this should resolve the issue."

If the issue persists, you may have to reinstall AEM from a fresh copy, install the update 1 package, restart (wait until error.log shows no more activity) and finally reinstall your installed packages manually.

Also, this could be the case, where you might have corrupted the indexes [Solution:- Stop AEM instance and delete Index files in crx-quickstart folder. restart Instance].

Last, check if bundles's dependencies are not present or packages dependencies are met or not.

 

Hope this helps!

Thanks

    vanegi
    Adobe Employee
    vanegiAdobe EmployeeAccepted solution
    Adobe Employee
    July 13, 2022

    Hi @akshaybhujbale,

    Please check the logs to verify the root cause. You may consider the following:

    1. run a data store consistency check for potential corruption.

    Fix Inconsistencies in the repository when SegmentNotFound Issue is reported in AEM 6.x

    2. run index consistency check and potential corruption.

    Use oak-run.jar to Manage Indexes

     

    Thanks !

     

      SantoshSai
      Community Advisor
      SantoshSaiCommunity Advisor
      Community Advisor
      July 13, 2022

      Hi @akshaybhujbale ,

      To fix this, either remove the Repoinit file from the configs if not using or replace it with a org.apache.sling.jcr.repoinit.RepositoryInitializer-.config file from both the project you are deploying and the /crx-quickstart/launchpad/config/org/apache/sling/jcr location in file system.

      Reference: https://github.com/adobe/aem-project-archetype/issues/852

      Additionally refer this: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-editor-is-not-loading-anything-and-when-we-restart-the/m-p/454747#M130705

      Hope that helps!

      Regards,

      Santosh

      Santosh Sai
        Terms & ConditionsAccessibility statement

        Loading footer...