Overview of Troubleshooting in AEM 6.2

Issue 1:
While doing the AEM server set up, when you up AEM 6.2 jar using "nosamplecontent" runmode and login the server using admin also, you won’t be able to see the repository in the crx repo.

Fig1: crx Repository Not visible

To solve this issue, you need to change the value of Root Path as "/crx/server" in "Apache Sling DavEx Servlet" OSGi Configuration.

Fig 2: Apache Sling DavEx Servlet

Issue 2:
In AEM 6.2, While opening the page, console shows the issue
“Uncaught ReferenceError: CQ is not defined”.

The solution which worked for me is: Add a dependency “cq.shared” in the
clientlib “/etc/clientlibs/foundation/main” and this issue will no more visible to you.

Issue 3:
When there are a lot of components/requests on a page(ideally more than1000)
in AEM 6.2 and we are also running samplecontent on our AEM, then sometimes
you are not able to go to edit Mode and encountered this exception
“org.apache.sling.api.request.

TooManyCallsException”, Because there are max sling requests already defined in an OSGi Configuration and to solve this issue and increase the size off sling requests.

To solve this issue, Go to the OSGi Configuration "Apache Sling Main Servlet"
and Increase (may be 10000) the "Number of calls per request".

Fig 3: Apache Sling Main Servlet