AEM 6.2 Siteadmin, login page not working | Community
Skip to main content
Level 3
May 11, 2018

AEM 6.2 Siteadmin, login page not working

  • May 11, 2018
  • 14 replies
  • 16342 views

Hi Community,

Am trying to start AEM 6.2 instance but seems like there is some issue with my system the siteadmin page, login page, welcome screen , package manager none of these are working. I have tried installing new jar, i have tried installing AEM 6, 6.1, 6.2 and 6.3 but to no avail, in all these instances i get the same error.

Login page gives the below error -

Cannot serve request to /libs/granite/core/content/login.html in /libs/granite/core/components/login/login.jsp

Exception:

Cannot serve request to /libs/granite/core/content/login.html in /libs/granite/core/components/login/login.jsp

Exception:

java.lang.NullPointerException

at org.apache.jsp.libs.granite.core.components.login.login_jsp._jspService(login_jsp.java:161)

at org.apache.sling.scripting.jsp.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)

at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:502)

at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:449)

at org.apache.sling.scripting.jsp.JspScriptEngineFactory.callJsp(JspScriptEngineFactory.java:284)

at org.apache.sling.scripting.jsp.JspScriptEngineFactory.access$100(JspScriptEngineFactory.java:102)

at org.apache.sling.scripting.jsp.JspScriptEngineFactory$JspScriptEngine.eval(JspScriptEngineFactory.java:536)

at org.apache.sling.scripting.core.impl.DefaultSlingScript.call(DefaultSlingScript.java:388)

at org.apache.sling.scripting.core.impl.DefaultSlingScript.eval(DefaultSlingScript.java:184)

at org.apache.sling.scripting.core.impl.DefaultSlingScript.service(DefaultSlingScript.java:491)

...

After I go to crx/de and login using admin creds, package manager, siteadmin and none other links work except felix console. I have checked the

bundles, everything seem to be fine and in active state.

Follwong are the error ---

http://localhost:4502/content/we-retail.html

Error during include of component '/libs/wcm/foundation/components/page'

Error Message:

org.apache.sling.api.scripting.ScriptEvaluationException: org.apache.sling.scripting.sightly.SightlyException: org.apache.sling.api.scripting.ScriptEvaluationException: org.apache.sling.scripting.sightly.SightlyException: org.apache.sling.api.scripting.ScriptEvaluationException: org.apache.sling.scripting.sightly.SightlyException: org.mozilla.javascript.EcmaError: ReferenceError: "currentPage" is not defined. (/libs/wcm/foundation/components/page/initwcm.js#26)

http://localhost:4502/crx/packmgr/

Resource at '/crx/packmgr/' not found: No resource found

Cannot serve request to /crx/packmgr/ in /libs/sling/servlet/errorhandler/404.jsp

Request Progress:

      0 TIMER_START{Request Processing} 0 COMMENT timer_end format is {<elapsed msec>,<timer name>} <optional message> 0 LOG Method=GET, PathInfo=/crx/packmgr/ 0 TIMER_START{ResourceResolution} 0 TIMER_END{0,ResourceResolution} URI=/crx/packmgr/ resolves to Resource=NonExistingResource, path=/crx/packmgr/ 0 LOG Resource Path Info: SlingRequestPathInfo: path='/crx/packmgr/', selectorString='null', extension='null', suffix='null' 0 TIMER_START{ServletResolution} 0 TIMER_START{resolveServlet(/crx/packmgr/)} 1 LOG {0}: no servlet found 1 TIMER_END{1,resolveServlet(/crx/packmgr/)} Using servlet org.apache.sling.servlets.get.DefaultGetServlet 1 TIMER_END{1,ServletResolution} URI=/crx/packmgr/ handled by Servlet=org.apache.sling.servlets.get.DefaultGetServlet 1 LOG Applying Requestfilters 1 LOG Calling filter: com.adobe.granite.resourceresolverhelper.impl.ResourceResolverHelperImpl 1 LOG Calling filter: org.apache.sling.bgservlets.impl.BackgroundServletStarterFilter 2 LOG Calling filter: com.adobe.granite.rest.impl.servlet.ApiResourceFilter 2 LOG Calling filter: org.apache.sling.i18n.impl.I18NFilter 2 LOG Calling filter: com.adobe.granite.httpcache.impl.InnerCacheFilter 2 LOG Calling filter: org.apache.sling.rewriter.impl.RewriterFilter 2 LOG Calling filter: com.adobe.cq.mcm.campaign.servlets.CampaignCopyTracker

http://localhost:4502/siteadmin

Internal Server Error

Cannot serve request to /siteadmin in /libs/cq/ui/components/widget/html.jsp

Exception:

java.lang.NullPointerException at org.apache.jsp.libs.cq.ui.components.widget.html_jsp._jspService(html_jsp.java:170) at org.apache.sling.scripting.jsp.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:725) at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:502) at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:449) at org.apache.sling.scripting.jsp.JspScriptEngineFactory.callJsp(JspScriptEngineFactory.java:284) at org.apache.sling.scripting.jsp.JspScriptEngineFactory.access$100(JspScriptEngineFactory.java:102) at org.apache.sling.scripting.jsp.JspScriptEngineFactory$JspScriptEngine.eval(JspScriptEngineFactory.java:536) at org.apache.sling.scripting.core.impl.DefaultSlingScript.call(DefaultSlingScript.java:388) at org.apache.sling.scripting.core.impl.DefaultSlingScript.eval(DefaultSlingScript.java:184)

I have tried removing indexes, restarting my system, uninstalling java 8 and installing java 7 and tried as well. but nothing seem to be working.

Can someone please help me out.

Thanks!!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

14 replies

Level 3
October 3, 2019

In my case this issue happens randomly. At first it was when I switched between branches of git. Not every time i switched but that seemed to be a trigger, The last time it happened I hadn't switched branch or anything. The work i was doing was only javascript and when i rebuilt AEM from scratch and uploaded my backup packages all was fine.

I understand this seems like broken code but i cant understand how it possibly could be.

Barely anything changes and even when i rebuild and use the same code it still works fine.

Just every now and then it breaks.

It does seem like maybe this is could be something corrupting in a cache created by AEM because it happens across browsers but i wouldn't know where to begin looking.

Level 2
October 3, 2019

As you mentioned, for same code it works and then after sometime for same code it doesn't work. It was exactly similar issue in my case. As I earlier said, I figured out the piece of code which was reading a cookie and decrypting it on every request. That cookie we were setting when we navigate through our website. Now when there is an old cookie and code tries to read that cookie it fails.

Clearing that cookie was making it work, but then after sometime or some other day we were facing this problem. Now we have handled that piece of code which reads cookie and decrypt it based on some condition. Since then we never faced this issue.

As similar to your case, I was also suspecting so many non related things. But finally analysing error.log and request.log files helped me to identify the root-cause.

But surely the pattern you mentioned suggests it is custom code which is making this issue. Try to analyse from log files. Hopefully that will help.

Thanks,

Lokesh Tripathi

sunjot16
Adobe Employee
Adobe Employee
October 3, 2019

12.05.2018 00:32:45.537 *ERROR* [0:0:0:0:0:0:0:1 [1526065365525] GET /projects.html HTTP/1.1] org.apache.sling.servlets.resolver.internal.SlingServletResolver Calling the error handler resulted in an error

java.lang.Error: Unresolved compilation problems:

Only a type can be imported. com.adobe.acs.commons.wcm.ComponentHelper resolves to a package

ComponentHelper cannot be resolved to a type

ComponentHelper cannot be resolved to a type

Seems as if there were some compilation problems regarding these packages.

Please verify if source and target compilers point to auto in /system/console/configMgr -> Apache Sling Java Script Handler, and that it helps resolve the issue.

Also, verify why these packages cannot be resolved to a type.

Love_Sharma
Level 4
April 30, 2021

If you don't see login screen, alternative is to login from http://localhost:4502/crx/de/index.jsp. Login through crx and then hit login screen, it should work.