AEM tools is not accessible | Community
Skip to main content
DPrakashRaj
Community Advisor
DPrakashRajCommunity Advisor
Community Advisor
November 21, 2019

AEM tools is not accessible

  • November 21, 2019
  • 7 replies
  • 14221 views

Hi,

Do any one has ever faced this issue. when i navigate to /miscadmin page in AEM it renders a blank page while server response is 200. All other pages load fine.

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

7 replies

U
Adobe Employee
user05162Adobe Employee
Adobe Employee
November 23, 2019

- Check if you are getting any error in the log files when trying to load miscadmin

- Open the developer console in browser and check for any errors in the console OR any failing requests in the network tab

-  Try upping the json.maximumresults  of the Apache Sling Get Servlet

DPrakashRaj
Community Advisor
DPrakashRajCommunity AdvisorAuthor
Community Advisor
November 24, 2019

Network tab shows response 200 ok. I tried updating the Json.maximumresults = 100000 but with no luck.

    Ankur_Khare
    Community Advisor
    Ankur_KhareCommunity Advisor
    Community Advisor
    November 25, 2019

    Able to access http://localhost:4502/miscadmin  on Aem 6.5 .

    Please check logs..

      Dipti_Chauhan
      Community Advisor
      Dipti_ChauhanCommunity Advisor
      Community Advisor
      November 25, 2019

      Hi

      Please check Apache sling GET servlet configuration (system/console/configMgr), And verify if enable Json in checked.

      Thanks

      Dipti

        DPrakashRaj
        Community Advisor
        DPrakashRajCommunity AdvisorAuthor
        Community Advisor
        November 25, 2019

        Yes, its enabled

          Nirmal_Jose
          Adobe Employee
          Nirmal_JoseAdobe Employee
          Adobe Employee
          November 25, 2019

          Did this happen after a SP installation ?

            DPrakashRaj
            Community Advisor
            DPrakashRajCommunity AdvisorAuthor
            Community Advisor
            November 25, 2019

            yes, it happens after we upgraded to 6.3.2.1. But it didn't started immediately after service pack installation

              W
              Adobe Employee
              WasilZeeAdobe Employee
              Adobe Employee
              November 25, 2019

              Try with parameter /miscadmin?debugClientLibs=true

                DPrakashRaj
                Community Advisor
                DPrakashRajCommunity AdvisorAuthor
                Community Advisor
                November 25, 2019

                Nothing new came up. same issue

                S
                Adobe Employee
                sssfaffaaaAdobe Employee
                Adobe Employee
                November 25, 2019

                Are you trying with admin user?

                DPrakashRaj
                Community Advisor
                DPrakashRajCommunity AdvisorAuthor
                Community Advisor
                November 25, 2019

                admin user also have same issue...

                DPrakashRaj
                Community Advisor
                DPrakashRajCommunity AdvisorAuthor
                Community Advisor
                November 26, 2019

                Thanks all for your opinion. i was able to fix it

                U
                Adobe Employee
                user05162Adobe Employee
                Adobe Employee
                November 26, 2019

                Can you share the root cause of the issue?

                DPrakashRaj
                Community Advisor
                DPrakashRajCommunity AdvisorAuthor
                Community Advisor
                November 26, 2019

                /libs/wcm/core/content/misc node get resolved to /miscadmin in aem and one of author has updated this node. That was the root cause of the issue. i reverted it back and it starts working.

                Terms & ConditionsAccessibility statement

                Loading footer...