ERROR - filenotfound when using quickstart SDK | Community
Skip to main content
V
Adobe Employee
Var-1Adobe Employee
Adobe Employee
June 13, 2022
Solved

ERROR - filenotfound when using quickstart SDK

  • June 13, 2022
  • 3 replies
  • 2933 views

 

 

Hello all,

I get this error when I start AEM author SDK in cmd. I am using java 11.0.15 . Someone, please help me with this.

Thanks in advance:) 

 

C:\Program Files\aem-sdk\author>java -jar aem-author-p4502.jar
Loading quickstart properties: default
Loading quickstart properties: instance
Low-memory action set to fork
Using 64bit VM settings, min.heap=1024MB, min permgen=256MB, default fork arguments=[-Xmx1024m, -XX:MaxPermSize=256m]
The JVM reports a heap size of 4032 MB, meets our expectation of 1024 MB +/- 20
Setting properties from filename 'C:/Program Files/aem-sdk/author/aem-author-p4502.jar'
Option '-quickstart.server.port' set to '4502' from filename aem-author-p4502.jar
The admin password for this instance hasn't been defined yet.
Please enter the desired admin password:
Please re-enter password:
Verbose option not active, closing stdin and redirecting stdout and stderr
Redirecting stdout to C:\Program Files\aem-sdk\author\crx-quickstart\logs\stdout.log
java.io.FileNotFoundException: C:\Program Files\aem-sdk\author\crx-quickstart\logs\stdout.log (The system cannot find the path specified)
at java.base/java.io.FileOutputStream.open0(Native Method)
at java.base/java.io.FileOutputStream.open(FileOutputStream.java:298)
at java.base/java.io.FileOutputStream.<init>(FileOutputStream.java:237)
at java.base/java.io.FileOutputStream.<init>(FileOutputStream.java:187)
at com.adobe.granite.quickstart.base.impl.exec.StandardStreamsHandler.switchToLogFiles(StandardStreamsHandler.java:85)
at com.adobe.granite.quickstart.base.impl.Quickstart.<init>(Quickstart.java:107)
at com.adobe.granite.quickstart.base.impl.Main.<init>(Main.java:911)
at com.adobe.granite.quickstart.base.impl.Main.main(Main.java:980)
Quickstart: aborting
MAIN process: shutdown hook
MAIN process: exiting

Best answer by Nirmal_Jose

Interesting, it could be due to some permission issues. Can you please try

1. Download the SDK file fresh once more to ensure JAR is not corrupted

2. Ensure you are admin like user

3. Create the aem-sdk dev setup in some more generic custom folder like D:\, not C:\Program Files like system generated folders

3 replies

ArpitVarshney
Community Advisor
ArpitVarshneyCommunity Advisor
Community Advisor
June 13, 2022

Hey @var-1 You can validate and try the below things:

  • Make sure the port 4502 or the one used by AEM should be available. If it is used by another process, either kill it or start your AEM in a different port.
  • Try running the command using admin mode.

If the above doesn't work, go to the crx-quickstart/logs folderand try to see any logs in error and share them here.

Regards,

Arpit Varshney

 

    V
    Adobe Employee
    Var-1Adobe EmployeeAuthor
    Adobe Employee
    June 13, 2022

    Thanks for your reply @arpitvarshney ,

                  I checked port 4502 and also tried to run in admin mode. Still, I get the same error.

                  But the thing is crx-quickstart folder itself is not generating while I run the quickstart jar file. This causes the filenotfound error.

     

      Himanshu_Jain
      Community Advisor
      Himanshu_JainCommunity Advisor
      Community Advisor
      June 13, 2022

      Check start.bat file config values 

      CQ_JVM_OPTS=-Xmx1024m -XX:MaxPermSize=256M

      Ref: https://stackoverflow.com/questions/59866778/aem-author-instance-is-not-responding

       

       

      Himanshu Jain
        V
        Adobe Employee
        Var-1Adobe EmployeeAuthor
        Adobe Employee
        June 13, 2022

        Thanks @himanshu_jain,

              Where can I find the start.bat file?

          Himanshu_Jain
          Community Advisor
          Himanshu_JainCommunity Advisor
          Community Advisor
          June 13, 2022

          unpack the jar file in crx-quickstart folder .Under that /bin /start.bat

          Himanshu Jain
            Nirmal_Jose
            Adobe Employee
            Nirmal_JoseAdobe EmployeeAccepted solution
            Adobe Employee
            June 13, 2022

            Interesting, it could be due to some permission issues. Can you please try

            1. Download the SDK file fresh once more to ensure JAR is not corrupted

            2. Ensure you are admin like user

            3. Create the aem-sdk dev setup in some more generic custom folder like D:\, not C:\Program Files like system generated folders

              Terms & ConditionsAccessibility statement

              Loading footer...