Expand my Community achievements bar.

Internal Server Error After Upgrading to AEM 6.2

Avatar

Level 9

Hi All,

We have recently migrated from AEM 6.0 SP3 to AEM 6.2 and deployed our project specific code.

When we try to open the application pages we are getting "Internal Server Error. Please try after some time." 

Anyone has any idea on this issue?

Thanks,

Kishore

8 Replies

Avatar

Level 10

This could be any number of reasons - file a ticket as support has a database of issues and can help you. 

Avatar

Employee

Hi Kishore,

Have you already checked all the known issues with 6.2[0]

Was the upgrade done in place or a content migration using CRX2OAK?

Before deploying your code, could you access all the standard consoles? System/console, CRXDE? After you deployed your code, can you access the standard consoles?

When starting your instance is there any exceptions in the error.log file?

The above investigations would allow us to help you better :)

Regards,

Opkar

[0]https://docs.adobe.com/docs/en/aem/6-2/release-notes/known-issues.html

Avatar

Level 9

Opkar Gill wrote...

Hi Kishore,

Have you already checked all the known issues with 6.2[0]

Was the upgrade done in place or a content migration using CRX2OAK?

Before deploying your code, could you access all the standard consoles? System/console, CRXDE? After you deployed your code, can you access the standard consoles?

When starting your instance is there any exceptions in the error.log file?

The above investigations would allow us to help you better :)

Regards,

Opkar

[0]https://docs.adobe.com/docs/en/aem/6-2/release-notes/known-issues.html

 

Thanks Opkar for your suggestions.

Before up-gradation i am able to access pages,standard consoles(system/console and CRXDE).

After up-gradation i am only able to access System/Console but not CRXDE and out application specific pages.

Thanks,

Kishore 

Avatar

Administrator

Hi 

I would request you to please share Error.log (any error there), and full detail browser log.

Which 500 error it is? (500.11,500.12,......500.100) 

                                                         
500.0Module or ISAPI error occurred.
500.11Application is shutting down on the web server.
500.12Application is busy restarting on the web server.
500.13Web server is too busy.
500.15Direct requests for Global.asax are not allowed.
500.19Configuration data is invalid.
500.21Module not recognized.
500.22An ASP.NET httpModules configuration does not apply in Managed Pipeline mode.
500.23An ASP.NET httpHandlers configuration does not apply in Managed Pipeline mode.
500.24An ASP.NET impersonation configuration does not apply in Managed Pipeline mode.
500.50A rewrite error occurred during RQ_BEGIN_REQUEST notification handling. A configuration or inbound rule execution error occurred.
500.51A rewrite error occurred during GL_PRE_BEGIN_REQUEST notification handling. A global configuration or global rule execution error occurred.
500.52A rewrite error occurred during RQ_SEND_RESPONSE notification handling. An outbound rule execution occurred.
500.53A rewrite error occurred during RQ_RELEASE_REQUEST_STATE notification handling. An outbound rule execution error occurred. The rule is configured to be executed before the output user cache gets updated.

If nothing is working, contact customer care (https://daycare.day.com/home/createaticket.html ).

Thanks and Regards

Kautuk Sahni



Kautuk Sahni

Avatar

Level 9

kautuksahni wrote...

Hi 

I would request you to please share Error.log (any error there), and full detail browser log.

Which 500 error it is? (500.11,500.12,......500.100) 

                                                         
500.0Module or ISAPI error occurred.
500.11Application is shutting down on the web server.
500.12Application is busy restarting on the web server.
500.13Web server is too busy.
500.15Direct requests for Global.asax are not allowed.
500.19Configuration data is invalid.
500.21Module not recognized.
500.22An ASP.NET httpModules configuration does not apply in Managed Pipeline mode.
500.23An ASP.NET httpHandlers configuration does not apply in Managed Pipeline mode.
500.24An ASP.NET impersonation configuration does not apply in Managed Pipeline mode.
500.50A rewrite error occurred during RQ_BEGIN_REQUEST notification handling. A configuration or inbound rule execution error occurred.
500.51A rewrite error occurred during GL_PRE_BEGIN_REQUEST notification handling. A global configuration or global rule execution error occurred.
500.52A rewrite error occurred during RQ_SEND_RESPONSE notification handling. An outbound rule execution occurred.
500.53A rewrite error occurred during RQ_RELEASE_REQUEST_STATE notification handling. An outbound rule execution error occurred. The rule is configured to be executed before the output user cache gets updated.

If nothing is working, contact customer care (https://daycare.day.com/home/createaticket.html ).

Thanks and Regards

Kautuk Sahni

 

org.apache.sling.api.scripting.ScriptEvaluationException: javax.servlet.ServletException: javax.servlet.jsp.JspException: Error while executing script header.jsp
    at org.apache.sling.scripting.core.impl.DefaultSlingScript.call(DefaultSlingScript.java:416)
    at org.apache.sling.scripting.core.impl.DefaultSlingScript.eval(DefaultSlingScript.java:184)
    at org.apache.sling.scripting.core.impl.DefaultSlingScript.service(DefaultSlingScript.java:491)
    at com.day.cq.wcm.tags.IncludeTag.includeScript(IncludeTag.java:178)
    at com.day.cq.wcm.tags.IncludeTag.doEndTag(IncludeTag.java:95)
    at org.apache.jsp.libs.foundation.components.page.page_jsp._jspx_meth_cq_005finclude_005f1(page_jsp.java:218)
    at org.apache.jsp.libs.foundation.components.page.page_jsp._jspService(page_jsp.java:173)
    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)
    at org.apache.sling.engine.impl.request.RequestData.service(RequestData.java:546)
    at org.apache.sling.engine.impl.filter.SlingComponentFilterChain.render(SlingComponentFilterChain.java:44)
    at org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:77)
    at com.day.cq.personalization.impl.TargetComponentFilter.doFilter(TargetComponentFilter.java:96)
    at org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:68)
    at com.day.cq.wcm.core.impl.WCMDebugFilter.doFilter(WCMDebugFilter.java:133)
    at org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:68)
    at com.day.cq.wcm.core.impl.WCMComponentFilter.doFilter(WCMComponentFilter.java:265)
    at org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:68)
    at com.day.cq.wcm.core.impl.WCMDeveloperModeFilter.doFilter(WCMDeveloperModeFilter.java:114)
    at org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:68)
    at org.apache.sling.engine.impl.SlingRequestProcessorImpl.processComponent(SlingRequestProcessorImpl.java:282)
    at org.apache.sling.engine.impl.SlingRequestProcessorImpl.dispatchRequest(SlingRequestProcessorImpl.java:322)
    at org.apache.sling.engine.impl.request.SlingRequestDispatcher.dispatch(SlingRequestDispatcher.java:211)
    at org.apache.sling.engine.impl.request.SlingRequestDispatcher.include(SlingRequestDispatcher.java:104)
    at com.day.cq.wcm.core.impl.WCMComponentFilter$ForwardRequestDispatcher.include(WCMComponentFilter.java:503)
    at org.apache.jsp.libs.cq.Page.Page_jsp._jspService(Page_jsp.java:106)
    at org.apache.sling.scripting.jsp.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)

Attached screenshot of full browser log.

Avatar

Employee

Are all the bundles active in the system console? You are also just showing the console log. You will get more information from the error.log

Regards,

Opkar

Avatar

Level 9

Opkar Gill wrote...

Are all the bundles active in the system console? You are also just showing the console log. You will get more information from the error.log

Regards,

Opkar

 

Additional Logs

20.05.2016 12:44:52.393 *ERROR* [0:0:0:0:0:0:0:1 [1463728492389] GET /editor.html/content/geometrixx/en/toolbar/contacts.html HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Uncaught SlingException
org.apache.sling.scripting.jsp.jasper.JasperException: /libs/fd/af/components/editors/rendercondition/template/template.jsp(31,0) The absolute uri: http://www.adobe.com/taglibs/guides/2.0 cannot be resolved in either web.xml or the jar files deployed with this application
    at org.apache.sling.scripting.jsp.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40)
    at org.apache.sling.scripting.jsp.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407)
    at org.apache.sling.scripting.jsp.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:88)
    at org.apache.sling.scripting.jsp.jasper.compiler.Parser.processIncludeDirective(Parser.java:334)
    at org.apache.sling.scripting.jsp.jasper.compiler.Parser.parseIncludeDirective(Parser.java:367)
    at org.apache.sling.scripting.jsp.jasper.compiler.Parser.parseDirective(Parser.java:459)
    at org.apache.sling.scripting.jsp.jasper.compiler.Parser.parseElements(Parser.java:1417)
    at org.apache.sling.scripting.jsp.jasper.compiler.Parser.parse(Parser.java:133)
    at org.apache.sling.scripting.jsp.jasper.compiler.ParserController.doParse(ParserController.java:216)
    at org.apache.sling.scripting.jsp.jasper.compiler.ParserController.parse(ParserController.java:103)
    at org.apache.sling.scripting.jsp.jasper.compiler.Compiler.generateJava(Compiler.java:167)
    at org.apache.sling.scripting.jsp.jasper.compiler.Compiler.compile(Compiler.java:305)
    at org.apache.sling.scripting.jsp.jasper.compiler.Compiler.compile(Compiler.java:285)
    at org.apache.sling.scripting.jsp.jasper.compiler.Compiler.compile(Compiler.java:272)
    at org.apache.sling.scripting.jsp.jasper.JspCompilationContext.compile(JspCompilationContext.java:490)
    at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.prepareServlet(JspServletWrapper.java:427)
    at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:486)
    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)

Avatar

Level 9

This issue has been fixed by installing ACS Commons package.

Thanks,

Kishore