AEM 6.5 Root node is not accessible | Community
Skip to main content
A
aemuser001
Level 5
April 26, 2021
Solved

AEM 6.5 Root node is not accessible

  • April 26, 2021
  • 2 replies
  • 3159 views

Hi,

When accessing the URL http://server:port/crx/explorer/nodetypes/index.jsp as admin I get the following error message:

Unable to retrieve node type manager probably due to insufficiant rights. Please login as a more priviledged user.
javax.jcr.AccessDeniedException: Root node is not accessible.

 

The etc/key access tab has the following setting.  Please advice.

Thanks,

Leena

 

Best answer by BrianKasingli

@aemuser001,

I found a solution from Adobe's down documentation : Unable to login to AEM instances due to missing cryptoservice acls - https://helpx.adobe.com/ca/experience-manager/kb/unable-to-login-to-aem-instances-due-to-missing-cryptoservice-ac.html

 

Take a look.

2 replies

BrianKasingli
Community Advisor and Adobe Champion
BrianKasingliCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
April 26, 2021

@aemuser001,

I found a solution from Adobe's down documentation : Unable to login to AEM instances due to missing cryptoservice acls - https://helpx.adobe.com/ca/experience-manager/kb/unable-to-login-to-aem-instances-due-to-missing-cryptoservice-ac.html

 

Take a look.

    A
    aemuser001Author
    Level 5
    April 27, 2021

    Hi Brian,

    I had already seen that link prior to posting the question here. 

    From the screen shot I had provided, since I am seeing the screenshot for the first time, it is not clear to me if all the permissions are present or denied. 

    Thanks,

    Leena

    Asutosh_Jena_
    Community Advisor
    Asutosh_Jena_Community Advisor
    Community Advisor
    April 27, 2021

    Hi @aemuser001 

     

    Are you logged in with "admin" user or any other user with "administrator" privilages?

    Can you try with "admin" user and see what error you are getting when you are trying to access the page.

     

    Also are you getting any error when you are starting the instance? Anything unusual in the logs?

     

    Thanks!

      A
      aemuser001Author
      Level 5
      April 27, 2021

      Hi Asutosh,

       

      My earlier post on admin password change was related to gathering information. I had not made any change to admin user. I log in as admin user. Just to give a background, we are planning to install a new bundle. We tried taking a snapshot of the server and database backup last month, and at that time the AEM Author stopped working. We are using Oracle database for the Author repository. Last week after database maintenance work the AEM Author instance started to work. 

      Yesterday we tried to prepare for the bundle installation again. I tested all the links including crx/explorer/nodetypes/index.jsp prior and after the database backup and all the links were accessible. After the server snapshot was taken, all the links are working expect this particular link.

       

      Will this error in any way affect the installation of the new bundle?

       

      There are nine *ERROR* from today's error.log. Please find the snippet below.

      27.04.2021 00:00:00.083 *ERROR* [sling-default-3-AdobeSignRefreshTokenScheduleJob] com.adobe.forms.foundation.oauth.model.OAuthConfigSlingModel Refresh Token not present for: /conf/global/settings/cloudconfigs/fdm/ms-dynamics-odata-cloud-service/jcr:content
      27.04.2021 00:00:00.199 *INFO* [sling-default-2-com.adobe.cq.wcm.translation.impl.scheduler.ScheduleRepeatTranslationProject] com.adobe.cq.wcm.translation.impl.scheduler.ScheduleRepeatTranslationProject Starting sync process now
      27.04.2021 00:00:00.288 *INFO* [sling-default-2-com.adobe.cq.wcm.translation.impl.scheduler.ScheduleRepeatTranslationProject] com.adobe.cq.wcm.translation.impl.scheduler.ScheduleRepeatTranslationProject Project: Reference Fragments [DE]
      27.04.2021 00:00:00.289 *INFO* [sling-default-2-com.adobe.cq.wcm.translation.impl.scheduler.ScheduleRepeatTranslationProject]

      Thanks,

      Leena

       

      Terms & ConditionsAccessibility statement

      Loading footer...