Not able to handle this error for AEM6.5 | Community
Skip to main content
Z
ZeelTr
February 11, 2024
Solved

Not able to handle this error for AEM6.5

  • February 11, 2024
  • 5 replies
  • 1147 views

 I am getting this error. Please guide me how to resolve it.

 

I followed this step: 

Open a new command-line terminal and perform the following actions.

  1. In an empty directory, clone the aem-guides-wknd repository:

    $ git clone git@github.com:adobe/aem-guides-wknd.git --branch tutorial/component-basics-start --single-branch
     
     

    Optionally, you can continue using the project generated in the previous chapter, Project Setup.

  2. Navigate into the aem-guides-wknd folder.

    $ cd aem-guides-wknd
     

  3. Build and deploy the project to a local instance of AEM with the following command:

    $ mvn clean install -PautoInstallSinglePackage
     
    NOTE

    If using AEM 6.5 or 6.4, append the classic profile to any Maven commands.

    $ mvn clean install -PautoInstallSinglePackage -Pclassic
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 aanchal-sikka

Hello @zeeltr 

 

I guess you are exploring AEM for learning purposes.

I would suggest recreating your AEM instance. Delete crx-quickstart folder and set up the instance again.

 

It will save you time and get started on learning journey.

 

Always start and stop the AEM instance gracefully. Assure that the server has stopped, before you shut down your system/restart AEM

 

5 replies

SureshDhulipudi
Community Advisor
SureshDhulipudiCommunity Advisor
Community Advisor
February 11, 2024

This error related or due to incomplete build or bundle start.

- Your bundle installation may be incomplete or corrupted - Check error log for more details

- Check Bundles in system console - Bundle status (some of the necessary bundles status may not be in Active state)

 

Try Restart AEM and check the Error logs.

    Imran Khan
    Community Advisor
    Imran KhanCommunity Advisor
    Community Advisor
    February 11, 2024

    Check error.log for the same time we gave build and package deployment for more details as this can give 503 due to multiple reasons.

      Jagadeesh_Prakash
      Community Advisor
      Jagadeesh_PrakashCommunity Advisor
      Community Advisor
      February 12, 2024

      @zeeltr  this is not because of the code that you build. It could be because you haven't started the server properly. Below debug steps could help you 

       

      1. Try starting the AEM serving as admin user

      2. Try clearing the index in the /crx-qucikstart/repository/index and restart the server

      3. check in error logs if their is any error for segmentation error. If yes, then I suggest you to re-install a new server. 

      4. When you re-install the server make sure to start in admin mode. 

       

      Let me know which one worked for you 

        A
        anshul__
        Level 2
        February 12, 2024

        You can try few of these steps:

        1. Check the bundle status if it is active. If it is in Resolved/Installed state, check if there is any error and try to resolve it otherwise try activating the bundle manually.

        2. Check the error logs to check if anything is breaking.

        3. Restart the AEM instance.

        This should probably resolve the issue and you should get the start page.

          aanchal-sikka
          Community Advisor
          aanchal-sikkaCommunity AdvisorAccepted solution
          Community Advisor
          February 12, 2024

          Hello @zeeltr 

           

          I guess you are exploring AEM for learning purposes.

          I would suggest recreating your AEM instance. Delete crx-quickstart folder and set up the instance again.

           

          It will save you time and get started on learning journey.

           

          Always start and stop the AEM instance gracefully. Assure that the server has stopped, before you shut down your system/restart AEM

           

          Aanchal Sikka
            Terms & ConditionsAccessibility statement

            Loading footer...