Can not login into AEM author after installed SP 6.5.16. | Community
Skip to main content
T
ThachNguyen141
Level 2
October 29, 2023
Solved

Can not login into AEM author after installed SP 6.5.16.

  • October 29, 2023
  • 4 replies
  • 2848 views

Hi guys,

After i installed the AEM SP 6.5.16 on my local environment, i start my AEM author instance but i can not login and facing error message on the browsers. Error details are as follows:

http://localhost:4502/libs/granite/core/content/login.html

HTTP ERROR 503 ServletResolver service missing, cannot service requests URI: / STATUS: 503 MESSAGE: ServletResolver service missing, cannot service requests SERVLET: org.apache.felix.http.base.internal.dispatch.DispatcherServlet-296ed922

Error meesage on error.log:

*ERROR* [discovery.connectors.common.runner.6876b6ae-abef-4a44-b8af-5a6019712340.connectorPinger] org.apache.sling.discovery.base.connectors.announcement.AnnouncementRegistryImpl checkExpiredAnnouncements: could not log in administratively when checking for expired announcements of slingId=6876b6ae-abef-4a44-b8af-5a6019712340: org.apache.sling.api.resource.LoginException: Cannot derive user name for bundle org.apache.sling.discovery.base [159] and sub service null org.apache.sling.api.resource.LoginException: Cannot derive user name for bundle org.apache.sling.discovery.base [159] and sub service null at org.apache.sling.resourceresolver.impl.ResourceResolverFactoryImpl.getServiceResourceResolver(ResourceResolverFactoryImpl.java:79) [org.apache.sling.resourceresolver:1.7.10.B004] at org.apache.sling.discovery.base.connectors.announcement.AnnouncementRegistryImpl.checkExpiredAnnouncements(AnnouncementRegistryImpl.java:507) [org.apache.sling.discovery.base:2.0.8] at org.apache.sling.discovery.base.commons.BaseViewChecker.doCheckView(BaseViewChecker.java:225) [org.apache.sling.discovery.base:2.0.8] at org.apache.sling.discovery.oak.pinger.OakViewChecker.doCheckView(OakViewChecker.java:304) [org.apache.sling.discovery.oak:1.2.22] at org.apache.sling.discovery.base.commons.BaseViewChecker.heartbeatAndCheckView(BaseViewChecker.java:167) [org.apache.sling.discovery.base:2.0.8] at org.apache.sling.discovery.base.commons.BaseViewChecker.run(BaseViewChecker.java:150) [org.apache.sling.discovery.base:2.0.8] at org.apache.sling.discovery.base.commons.PeriodicBackgroundJob.safelyRun(PeriodicBackgroundJob.java:86) [org.apache.sling.discovery.base:2.0.8] at org.apache.sling.discovery.base.commons.PeriodicBackgroundJob.run(PeriodicBackgroundJob.java:77) [org.apache.sling.discovery.base:2.0.8] at java.lang.Thread.run(Unknown Source)

Please suggest solution to resolve this issue.

Thank you so much,

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 kautuk_sahni

@thachnguyen141 

The error message HTTP ERROR 503 ServletResolver service missing, cannot service requests indicates that AEM is unable to start the ServletResolver service, which is responsible for resolving and dispatching requests to the appropriate servlets.

The error message on the error.log file indicates that AEM is unable to log in administratively when checking for expired announcements of the Sling discovery connector. This is likely because the ServletResolver service is not running.

To resolve this issue, you can try the following:

  1. Restart the AEM author instance. This may resolve the issue if it was caused by a temporary glitch.
  2. Check the AEM log files for any other errors. The log files may provide additional information about the cause of the problem.
  3. Verify that you are using the correct version of the AEM SP 6.5.16 package. Make sure that the package is compatible with your version of AEM and your operating system.
  4. Try reinstalling the AEM SP 6.5.16 package. If the package is corrupted or incomplete, reinstalling it may resolve the issue.
  5. Contact Adobe support for assistance. If you are unable to resolve the issue on your own, you can contact Adobe support for assistance.

Here are some additional tips for resolving AEM login issues:

  • Make sure that you are using the correct username and password.
  • Make sure that the user account is enabled and has the appropriate permissions.
  • Try logging in using a different web browser.
  • Clear the browser cache and cookies.
  • Disable any browser extensions or add-ons that may be interfering with AEM.
  • Try logging in from a different computer.

If you are still unable to log in to AEM, please contact Adobe support for assistance.

4 replies

Lokesh_Vajrala
Community Advisor
Lokesh_VajralaCommunity Advisor
Community Advisor
October 30, 2023

Hi @thachnguyen141 

 

It looks like instance has not started up completely to operate. Based on the error you shared, it is missing the sling discovery service user in the instance. What other errors you see in the error.log while the instance is starting up? 

 

Thanks,

Lokesh

    T
    ThachNguyen141Author
    Level 2
    October 30, 2023

    Hi @lokesh_vajrala ,

    I have added other errors in the error.log while my author instance is starting up. Thank you for your help.

    30.10.2023 07:23:13.186 *INFO* [FelixStartLevel] com.adobe.granite.crx-explorer BundleEvent STARTED 30.10.2023 07:23:13.197 *INFO* [FelixStartLevel] com.adobe.granite.crx-packagemgr BundleEvent RESOLVED 30.10.2023 07:23:13.198 *INFO* [FelixStartLevel] com.adobe.granite.crx-packagemgr BundleEvent STARTING 30.10.2023 07:23:13.233 *INFO* [FelixStartLevel] com.adobe.granite.crx-packagemgr Service [com.day.crx.packaging.impl.SlingInstallerSupportImpl,1481, [com.day.crx.packaging.impl.SlingInstallerSupport]] ServiceEvent REGISTERED 30.10.2023 07:23:13.237 *WARN* [FelixStartLevel] org.apache.sling.jcr.resource.internal.JcrSystemUserValidator The provided service principal name 'sling-installer-service' is not a known JCR system user id and therefore not allowed in the Sling Service User Mapper. 30.10.2023 07:23:13.240 *ERROR* [FelixStartLevel] com.day.crx.packaging.impl.SlingInstallerSupportImpl Unable to clean up orphaned markers. javax.jcr.LoginException: Can neither derive user name nor principal names for bundle com.adobe.granite.crx-packagemgr [240] and sub service slingInstallerService at org.apache.sling.jcr.base.AbstractSlingRepository2.loginService(AbstractSlingRepository2.java:387) [org.apache.sling.jcr.base:3.1.6] at com.day.crx.packaging.impl.SlingInstallerSupportImpl.login(SlingInstallerSupportImpl.java:111) [com.adobe.granite.crx-packagemgr:1.2.80.CQ650-B0040] at com.day.crx.packaging.impl.SlingInstallerSupportImpl.cleanupOrphanedMarkers(SlingInstallerSupportImpl.java:122) [com.adobe.granite.crx-packagemgr:1.2.80.CQ650-B0040] at com.day.crx.packaging.impl.SlingInstallerSupportImpl.activate(SlingInstallerSupportImpl.java:74) [com.adobe.granite.crx-packagemgr:1.2.80.CQ650-B0040] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 30.10.2023 07:23:14.300 *INFO* [FelixStartLevel] org.apache.sling.resourceresolver Service [org.apache.sling.resourceresolver.impl.console.ResourceResolverWebConsolePlugin,1576, [javax.servlet.Servlet]] ServiceEvent REGISTERED 30.10.2023 07:23:14.307 *WARN* [FelixStartLevel] org.apache.sling.jcr.resource.internal.JcrSystemUserValidator The provided service principal name 'repository-reader-service' is not a known JCR system user id and therefore not allowed in the Sling Service User Mapper. 30.10.2023 07:23:14.307 *ERROR* [FelixStartLevel] org.apache.sling.resourceresolver.impl.CommonResourceResolverFactoryImpl activate: Cannot access repository, failed setting up Mapping Support org.apache.sling.api.resource.LoginException: Cannot derive user name or principal names for bundle org.apache.sling.resourceresolver [166] and sub service mapping at org.apache.sling.resourceresolver.impl.CommonResourceResolverFactoryImpl.getServiceUserAuthenticationInfo(CommonResourceResolverFactoryImpl.java:504) [org.apache.sling.resourceresolver:1.7.10.B004] at org.apache.sling.resourceresolver.impl.mapping.MapEntries.<init>(MapEntries.java:136) [org.apache.sling.resourceresolver:1.7.10.B004] at org.apache.sling.resourceresolver.impl.CommonResourceResolverFactoryImpl.activate(CommonResourceResolverFactoryImpl.java:318) [org.apache.sling.resourceresolver:1.7.10.B004] at org.apache.sling.resourceresolver.impl.ResourceResolverFactoryActivator.registerFactory(ResourceResolverFactoryActivator.java:518) [org.apache.sling.resourceresolver:1.7.10.B004] at org.apache.sling.resourceresolver.impl.ResourceResolverFactoryActivator.checkFactoryPreconditions(ResourceResolverFactoryActivator.java:582) [org.apache.sling.resourceresolver:1.7.10.B004] at org.apache.sling.resourceresolver.impl.ResourceResolverFactoryActivator.access$100(ResourceResolverFactoryActivator.java:68) [org.apache.sling.resourceresolver:1.7.10.B004] 30.10.2023 07:23:18.126 *ERROR* [FelixStartLevel] com.adobe.granite.workflow.core bundle com.adobe.granite.workflow.core:2.0.240.CQ660-B0017 (296)[com.adobe.granite.workflow.core.launcher.WorkflowLauncherListener(1048)] : The activate method has thrown an exception (java.lang.RuntimeException: Error logging in as service user) java.lang.RuntimeException: Error logging in as service user at com.adobe.granite.workflow.core.util.ServiceLoginUtil.getRepositoryReadSession(ServiceLoginUtil.java:96) [com.adobe.granite.workflow.core:2.0.240.CQ660-B0017] at com.adobe.granite.workflow.core.launcher.WorkflowLauncherListener.start(WorkflowLauncherListener.java:638) [com.adobe.granite.workflow.core:2.0.240.CQ660-B0017] at com.adobe.granite.workflow.core.launcher.WorkflowLauncherListener.activate(WorkflowLauncherListener.java:550) [com.adobe.granite.workflow.core:2.0.240.CQ660-B0017] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.felix.scr.impl.inject.methods.BaseMethod.invokeMethod(BaseMethod.java:242) [org.apache.felix.scr:2.1.20] at org.apache.felix.scr.impl.inject.methods.BaseMethod.access$500(BaseMethod.java:41) [org.apache.felix.scr:2.1.20] at org.apache.felix.scr.impl.inject.methods.BaseMethod$Resolved.invoke(BaseMethod.java:678) [org.apache.felix.scr:2.1.20] at org.apache.felix.scr.impl.inject.methods.BaseMethod.invoke(BaseMethod.java:524) [org.apache.felix.scr:2.1.20] at org.apache.felix.scr.impl.inject.methods.ActivateMethod.invoke(ActivateMethod.java:318) [org.apache.felix.scr:2.1.20] at org.apache.felix.scr.impl.inject.methods.ActivateMethod.invoke(ActivateMethod.java:308) [org.apache.felix.scr:2.1.20] at org.apache.felix.scr.impl.manager.SingleComponentManager.createImplementationObject(SingleComponentManager.java:342) [org.apache.felix.scr:2.1.20] at org.apache.felix.scr.impl.manager.SingleComponentManager.createComponent(SingleComponentManager.java:115) [org.apache.felix.scr:2.1.20] at org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:984) [org.apache.felix.scr:2.1.20] at org.apache.felix.scr.impl.manager.SingleComponentManager.getServiceInternal(SingleComponentManager.java:957) [org.apache.felix.scr:2.1.20] ... Caused by: javax.jcr.LoginException: Can neither derive user name nor principal names for bundle com.adobe.granite.workflow.core [296] and sub service repo-reader at org.apache.sling.jcr.base.AbstractSlingRepository2.loginService(AbstractSlingRepository2.java:387) [org.apache.sling.jcr.base:3.1.6] at com.adobe.granite.workflow.core.util.ServiceLoginUtil.getRepositoryReadSession(ServiceLoginUtil.java:94) [com.adobe.granite.workflow.core:2.0.240.CQ660-B0017] ... 62 common frames omitted 30.10.2023 07:23:18.154 *WARN* [FelixStartLevel] org.apache.sling.jcr.resource.internal.JcrSystemUserValidator The provided service principal name 'workflow-service' is not a known JCR system user id and therefore not allowed in the Sling Service User Mapper. 30.10.2023 07:23:18.155 *ERROR* [FelixStartLevel] com.adobe.granite.workflow.core bundle com.adobe.granite.workflow.core:2.0.240.CQ660-B0017 (296)[com.adobe.granite.workflow.core.eventsupport.JcrToWorkflowEventService(1065)] : The activate method has thrown an exception (java.lang.RuntimeException: Error logging in as service user) java.lang.RuntimeException: Error logging in as service user at com.adobe.granite.workflow.core.util.ServiceLoginUtil.getWorkflowInstanceDataSession(ServiceLoginUtil.java:60) [com.adobe.granite.workflow.core:2.0.240.CQ660-B0017] at com.adobe.granite.workflow.core.eventsupport.JcrToWorkflowEventService.activate(JcrToWorkflowEventService.java:129) [com.adobe.granite.workflow.core:2.0.240.CQ660-B0017] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.felix.scr.impl.inject.methods.BaseMethod.invokeMethod(BaseMethod.java:242) [org.apache.felix.scr:2.1.20] at org.apache.felix.scr.impl.inject.methods.BaseMethod.access$500(BaseMethod.java:41) [org.apache.felix.scr:2.1.20] at org.apache.felix.scr.impl.inject.methods.BaseMethod$Resolved.invoke(BaseMethod.java:678) [org.apache.felix.scr:2.1.20] at org.apache.felix.scr.impl.inject.methods.BaseMethod.invoke(BaseMethod.java:524) [org.apache.felix.scr:2.1.20] at org.apache.felix.scr.impl.inject.methods.ActivateMethod.invoke(ActivateMethod.java:318) [org.apache.felix.scr:2.1.20] at org.apache.felix.scr.impl.inject.methods.ActivateMethod.invoke(ActivateMethod.java:308) [org.apache.felix.scr:2.1.20] at org.apache.felix.scr.impl.manager.SingleComponentManager.createImplementationObject(SingleComponentManager.java:342) [org.apache.felix.scr:2.1.20] at org.apache.felix.scr.impl.manager.SingleComponentManager.createComponent(SingleComponentManager.java:115) [org.apache.felix.scr:2.1.20] at org.apache.felix.scr.impl.manager.SingleComponentManager.getService(SingleComponentManager.java:984) [org.apache.felix.scr:2.1.20] at org.apache.felix.scr.impl.manager.SingleComponentManager.getServiceInternal(SingleComponentManager.java:957) [org.apache.felix.scr:2.1.20] at org.apache.felix.scr.impl.manager.AbstractComponentManager.activateInternal(AbstractComponentManager.java:766) [org.apache.felix.scr:2.1.20] ... Caused by: javax.jcr.LoginException: Can neither derive user name nor principal names for bundle com.adobe.granite.workflow.core [296] and sub service workflow at org.apache.sling.jcr.base.AbstractSlingRepository2.loginService(AbstractSlingRepository2.java:387) [org.apache.sling.jcr.base:3.1.6] at com.adobe.granite.workflow.core.util.ServiceLoginUtil.getWorkflowInstanceDataSession(ServiceLoginUtil.java:58) [com.adobe.granite.workflow.core:2.0.240.CQ660-B0017] ... 38 common frames omitted 30.10.2023 07:23:18.218 *WARN* [FelixStartLevel] org.apache.sling.jcr.resource.internal.JcrSystemUserValidator The provided service principal name 'repository-reader-service' is not a known JCR system user id and therefore not allowed in the Sling Service User Mapper. 30.10.2023 07:23:18.219 *ERROR* [FelixStartLevel] com.adobe.granite.workflow.core bundle com.adobe.granite.workflow.core:2.0.240.CQ660-B0017 (296)[com.adobe.granite.workflow.core.collection.ResourceCollectionManagerListener(1043)] : The activate method has thrown an exception (java.lang.RuntimeException: Error logging in as service user) java.lang.RuntimeException: Error logging in as service user at com.adobe.granite.workflow.core.util.ServiceLoginUtil.getRepositoryReadSession(ServiceLoginUtil.java:96) [com.adobe.granite.workflow.core:2.0.240.CQ660-B0017] at com.adobe.granite.workflow.core.collection.ResourceCollectionManagerListener.activate(ResourceCollectionManagerListener.java:159) [com.adobe.granite.workflow.core:2.0.240.CQ660-B0017] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) ... Caused by: javax.jcr.LoginException: Can neither derive user name nor principal names for bundle com.adobe.granite.workflow.core [296] and sub service repo-reader at org.apache.sling.jcr.base.AbstractSlingRepository2.loginService(AbstractSlingRepository2.java:387) [org.apache.sling.jcr.base:3.1.6] at com.adobe.granite.workflow.core.util.ServiceLoginUtil.getRepositoryReadSession(ServiceLoginUtil.java:94) [com.adobe.granite.workflow.core:2.0.240.CQ660-B0017] ... 57 common frames omitted

     

    Regards,

    Thach

      J
      Jeevan-Eranti
      Level 2
      October 30, 2023

      Hi @ThachNguyen141 

       

      Please check if the bundles are active in the Web console (/system/console). If all bundles are active, then please stop the instance, navigate to the "crx-quickstart\launchpad\config\org\apache\sling/jcr/repoinit" directory, and delete the files within the repoinit folder. Afterward, start the AEM instance and check it.

        T
        ThachNguyen141Author
        Level 2
        October 31, 2023

        Hi @jeevan-eranti 

        I applied your way but the issue still happening on my end.

        Thank you so much.

          T
          ThachNguyen141Author
          Level 2
          October 31, 2023

          @thachnguyen141  so you can login through webconsole - /system/console? If you're, are all bundles active?  


          Hi @lokesh_vajrala 

          Yes, i can login through crxde, system/console/, All my bundles are actived. I have attacked images. Please check them.

          Thanks.

            DPrakashRaj
            Community Advisor
            DPrakashRajCommunity Advisor
            Community Advisor
            October 30, 2023

            What was the prior version of aem service pack before installing sp16?

              T
              ThachNguyen141Author
              Level 2
              October 31, 2023

              Hi @dprakashraj

              My prior version of AEM was 6.5.11 before installing SP16

              Thank you so much.

                kautuk_sahni
                Community Manager
                kautuk_sahniCommunity Manager
                Community Manager
                November 1, 2023

                @thachnguyen141 Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

                Kautuk Sahni
                  T
                  ThachNguyen141Author
                  Level 2
                  November 2, 2023

                  Hi @kautuk_sahni,

                  I have tried to install the SP 16 again but the issue is still happening. Do you have any sugesstion for me?

                  Thank you so much.

                  Thach

                    kautuk_sahni
                    Community Manager
                    kautuk_sahniCommunity ManagerAccepted solution
                    Community Manager
                    November 2, 2023

                    @thachnguyen141 

                    The error message HTTP ERROR 503 ServletResolver service missing, cannot service requests indicates that AEM is unable to start the ServletResolver service, which is responsible for resolving and dispatching requests to the appropriate servlets.

                    The error message on the error.log file indicates that AEM is unable to log in administratively when checking for expired announcements of the Sling discovery connector. This is likely because the ServletResolver service is not running.

                    To resolve this issue, you can try the following:

                    1. Restart the AEM author instance. This may resolve the issue if it was caused by a temporary glitch.
                    2. Check the AEM log files for any other errors. The log files may provide additional information about the cause of the problem.
                    3. Verify that you are using the correct version of the AEM SP 6.5.16 package. Make sure that the package is compatible with your version of AEM and your operating system.
                    4. Try reinstalling the AEM SP 6.5.16 package. If the package is corrupted or incomplete, reinstalling it may resolve the issue.
                    5. Contact Adobe support for assistance. If you are unable to resolve the issue on your own, you can contact Adobe support for assistance.

                    Here are some additional tips for resolving AEM login issues:

                    • Make sure that you are using the correct username and password.
                    • Make sure that the user account is enabled and has the appropriate permissions.
                    • Try logging in using a different web browser.
                    • Clear the browser cache and cookies.
                    • Disable any browser extensions or add-ons that may be interfering with AEM.
                    • Try logging in from a different computer.

                    If you are still unable to log in to AEM, please contact Adobe support for assistance.

                    Kautuk Sahni
                      Terms & ConditionsAccessibility statement

                      Loading footer...