Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

HTTP ERROR 503 ServletResolver service missing, cannot service requests

Avatar

Level 4

Hi,

 

I am trying to login into my instance and I am getting this error.

HTTP ERROR 503 ServletResolver service missing, cannot service requests

URI: /libs/granite/core/content/login.html
STATUS: 503
MESSAGE: ServletResolver service missing, cannot service requests
SERVLET: org.apache.felix.http.base.internal.dispatch.DispatcherServlet-71190bb2

 

I am using AEM 6.5 Service pack 12

Any suggestion I can use to resolve this issue?

 

Thank You

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

Most likely there's a problem with the repository. I wrote a blog article about it: https://cqdump.joerghoh.de/2022/03/17/how-to-analyze-authentication-support-missing/ can you check that?

View solution in original post

5 Replies

Avatar

Community Advisor

Hi @StrawHatM23 ,

Please check if there are any bundles in Installed state here: http://localhost:4502/system/console/bundles

Regards,

Santosh

Avatar

Level 4

Hi,

 

When I click the link I am not able to log in, that error still shows up.

Avatar

Community Advisor

Is your project installed on AEM instance? If Yes Can you try setting up fresh instance without your project? In this case we can able to find out whether it's issue with AEM or your code.

Avatar

Correct answer by
Employee Advisor

Most likely there's a problem with the repository. I wrote a blog article about it: https://cqdump.joerghoh.de/2022/03/17/how-to-analyze-authentication-support-missing/ can you check that?

Avatar

Level 2

Check your log, most likely you can find the error or warning or whatever the latest change you made to cause the server error.
1. Easy way: For this case, got to {AEM_ROOT}\crx-quickstart\launchpad\config\org\apache\sling\serviceusermapping\impl\ServiceUserMapperImpl.config, change the require.validation to false. then the server will start and everything goes back to normal.
2. Hard way: keep the require.validation=true, but add the service user to jaas.config or wherever the AEM can validate the service user.