unable to restart AEM SDK by clicking start.bat or quickstart.bat files | Community
Skip to main content
G
georhe6
Level 4
May 10, 2024
Solved

unable to restart AEM SDK by clicking start.bat or quickstart.bat files

  • May 10, 2024
  • 3 replies
  • 1767 views

Hi Team,

I have received vanilla AEM sdk jar (not using licence.properties along with the jar) and renamed the jar into aem-author-p4502.jar then i started the instance by the command java -jar aem-author-p4502.jar.

The instance started successfully, and the bundles are up and running and pages are loading as expected.There are no errors observed in error.logs file.

 

However, after shutdown (Ctrl+C), when I tried to start the instance from start.bat or quickstart.bat, the command prompt window briefly appears and then disappears without any further action. Essentially, I'm unable to restart the instance once I've stopped it following the initial startup.

 

  • not using licence.properties along with the jar
  • Windows machine
  • java version "11.0.21" 2023-10-17 LTS
  • aem-sdk-quickstart-2023.12.14697.20231215T125030Z-231200.jar

 

 

Thanks in advance.

 

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 georhe6

Hi Team,

The issue is resolved now. This had nothing to do with AEM. Unfortunately, execution access on the .bat file was restricted by the IT support team. By running it as an administrator, the .bat files are now executing properly.

 

Thanks 

Geo

3 replies

Saravanan_Dharmaraj
Community Advisor
Saravanan_DharmarajCommunity Advisor
Community Advisor
May 10, 2024

@georhe6 Have you checked this official documentation on how to start the SDK jar 

https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/local-development-environment-set-up/aem-runtime

  1. Start the local AEM Author Service by executing the following from the command line:

    • java -jar aem-author-p4502.jar
      • Provide the admin password as admin. Any admin password is acceptable, however it is recommend to use the default for local development to reduce the need to reconfigure.

    You cannot start the AEM as Cloud Service Quickstart Jar by double-clicking.

    G
    georhe6Author
    Level 4
    May 10, 2024

    Hi @saravanan_dharmaraj ,

    Thanks for the response.
    I followed the official documentation provided by Adobe.
    I started the instance through CMD by this command java -jar aem-author-p4502.jar as mentioned in the post.
    Yes, I read in the AEM as Cloud Service official article that the double click starting is not recommended.

     

    Thanks,

    Geo

     

      EstebanBustamante
      Community Advisor and Adobe Champion
      EstebanBustamanteCommunity Advisor and Adobe Champion
      Community Advisor and Adobe Champion
      May 10, 2024

      I don't fully understand your question, but if you start AEM using the script under the bin folder, then you must stop it using the stop script under the bin folder.

       

      Hope this helps.

      Esteban Bustamante
        G
        georhe6Author
        Level 4
        May 10, 2024

        Hi @estebanbustamante ,

         The initial start of the instance I executing the following from the command line:java -jar aem-author-p4502.jar

        It populated the crx-quickstart folder and all files as expected . The instance started normally without any error.
        I shut down the instance using the command CTRL+C in command line.
        And then if I access the start.bat/quickstart.bat file the server is not getting started again. That is the issue.


          G
          georhe6AuthorAccepted solution
          Level 4
          May 13, 2024

          Hi Team,

          The issue is resolved now. This had nothing to do with AEM. Unfortunately, execution access on the .bat file was restricted by the IT support team. By running it as an administrator, the .bat files are now executing properly.

           

          Thanks 

          Geo

            Terms & ConditionsAccessibility statement

            Loading footer...