Can't edit any page. AEM trying to load component that no longer exists | Community
Skip to main content
D
dds3455
November 17, 2020
Solved

Can't edit any page. AEM trying to load component that no longer exists

  • November 17, 2020
  • 5 replies
  • 3041 views

I can't load any page in the editor. AEM is complaining in my browser console that a component doesn't exist. That component is from a previous AEM installation. Why does my new installation still have a reference to this old component?

 

granite.js:234 GET http://localhost:4502/content/connectapp/en/DashboardBanner/jcr:content/par/banner.html?forceeditcontext=true&_=1605590388793 404 (Not Found)

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

Hi,

Could you please confirm on below-

1. Have u created a copy of ur old server?

2. If not then have u installed any package on vanilla instance

3. If yes then go to content/connectapp/en/DashboardBanner/jcr:content/par/banner. this node and check if its present and there and corresponding references are present?

5 replies

Umesh_Thakur
Community Advisor
Umesh_ThakurCommunity Advisor
Community Advisor
November 17, 2020

Can you try after clearing browser cache or in incognito

    Anudeep_Garnepudi
    Community Advisor
    Anudeep_GarnepudiCommunity Advisor
    Community Advisor
    November 17, 2020

    Hi @dds3455 

    Though the component doesn't exist, the page you are trying to access might have the reference of the old component. Go to crxde check and try to delete the reference(/content/connectapp/en/DashboardBanner/jcr:content/par/banner) of the component under the page.

    AG

    AG
      Suraj_Kamdi
      Community Advisor
      Suraj_KamdiCommunity Advisor
      Community Advisor
      November 17, 2020

      @dds3455 

      This happens mainly because of invalid references. There might be a possibility that someone has removed the old component or so.

       

      Please check the error.log and see the root cause issue and try deleting that resource or remove the reference from the page.

      This might help you to resolve your issue.

       

        Ankur_Khare
        Community Advisor
        Ankur_KhareCommunity AdvisorAccepted solution
        Community Advisor
        November 17, 2020

        Hi,

        Could you please confirm on below-

        1. Have u created a copy of ur old server?

        2. If not then have u installed any package on vanilla instance

        3. If yes then go to content/connectapp/en/DashboardBanner/jcr:content/par/banner. this node and check if its present and there and corresponding references are present?

          D
          dds3455Author
          November 18, 2020

          Thanks for the suggestions. The problem was happening in AEM 6.3. I installed AEM 6.5 and I no longer have the issue.

            Terms & ConditionsAccessibility statement

            Loading footer...