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.
Thanks in advance.
Solved! Go to Solution.
Views
Replies
Total Likes
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
@george6 Have you checked this official documentation on how to start the SDK jar
Start the local AEM Author Service by executing the following from the command line:
java -jar aem-author-p4502.jar
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.
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
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.
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.
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
Views
Likes
Replies