Internal Server Error After Upgrading to AEM 6.2 | Community
Skip to main content
GK-007
GK-007
Level 9
May 14, 2016

Internal Server Error After Upgrading to AEM 6.2

  • May 14, 2016
  • 2 replies
  • 4158 views

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

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

2 replies

smacdonald2008
smacdonald2008
Level 10
May 14, 2016

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

O
Adobe Employee
ogillAdobe Employee
Adobe Employee
May 14, 2016

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

GK-007
GK-007Author
Level 9
May 16, 2016

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 

GK-007
GK-007Author
Level 9
June 4, 2016

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)


This issue has been fixed by installing ACS Commons package.

Thanks,

Kishore

Terms & ConditionsAccessibility statement

Loading footer...