D:\SonarQube\sonarqube-10.2.0.77647\bin\windows-x86-64>StartSonar.bat
Starting SonarQube…
Unrecognized option: --add-exports=java.base/jdk.internal.ref=ALL-UNNAMED
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Welcome Thomas 
what’s your Java version ? Sonarqube 10.2 needs Java 17 to run, guess you’re using an older version.
Gilbert
Hello, the version is 1.8.0_381.
This means you need to use Java 17 instead.
see i.e https://adoptium.net/de/temurin/releases/ for jdk-17.0.8.1
thank you I got past that by upgrading java, now I am having trouble with the drivers:
D:\SonarQube\sonarqube-10.2.0.77647\bin\windows-x86-64>
D:\SonarQube\sonarqube-10.2.0.77647\bin\windows-x86-64>java -version
java version “17.0.8” 2023-07-18 LTS
Java™ SE Runtime Environment (build 17.0.8+9-LTS-211)
Java HotSpot™ 64-Bit Server VM (build 17.0.8+9-LTS-211, mixed mode, sharing)
D:\SonarQube\sonarqube-10.2.0.77647\bin\windows-x86-64>
D:\SonarQube\sonarqube-10.2.0.77647\bin\windows-x86-64>
D:\SonarQube\sonarqube-10.2.0.77647\bin\windows-x86-64>StartSonar.bat
Starting SonarQube…
Exception in thread “main” org.sonar.process.MessageException: Unsupported JDBC driver provider: devfsbmsq004
D:\SonarQube\sonarqube-10.2.0.77647\bin\windows-x86-64>
D:\SonarQube\sonarqube-10.2.0.77647\bin\windows-x86-64>
Sorry to keep posting so much, here is what I am getting now:
D:\SonarQube\sonarqube-10.2.0.77647\bin\windows-x86-64>StartSonar.bat
Starting SonarQube…
2023.09.11 16:06:02 INFO app[o.s.a.AppFileSystem] Cleaning or creating temp directory D:\SonarQube\sonarqube-10.2.0.77647\temp
2023.09.11 16:06:02 ERROR app[o.s.a.p.ManagedProcessHandler] Failed to launch process [ElasticSearch]
java.lang.NumberFormatException: For input string: “”
at java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:67)
at java.base/java.lang.Integer.parseInt(Integer.java:678)
at java.base/java.lang.Integer.parseInt(Integer.java:786)
at org.sonar.application.es.EsSettings.configureNetwork(EsSettings.java:167)
at org.sonar.application.es.EsSettings.build(EsSettings.java:100)
at org.sonar.application.command.CommandFactoryImpl.createEsInstallation(CommandFactoryImpl.java:111)
at org.sonar.application.command.CommandFactoryImpl.createEsCommand(CommandFactoryImpl.java:98)
at org.sonar.application.SchedulerImpl.lambda$tryToStartProcess$2(SchedulerImpl.java:191)
at org.sonar.application.process.ManagedProcessHandler.start(ManagedProcessHandler.java:76)
at org.sonar.application.SchedulerImpl.tryToStartProcess(SchedulerImpl.java:190)
at org.sonar.application.SchedulerImpl.tryToStartEs(SchedulerImpl.java:142)
at org.sonar.application.SchedulerImpl.tryToStartAll(SchedulerImpl.java:134)
at org.sonar.application.SchedulerImpl.schedule(SchedulerImpl.java:113)
at org.sonar.application.App.start(App.java:59)
at org.sonar.application.App.main(App.java:81)
2023.09.11 16:06:02 INFO app[o.s.a.SchedulerImpl] Process[ElasticSearch] is stopped
2023.09.11 16:06:02 INFO app[o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
2023.09.11 16:06:02 INFO app[o.s.a.SchedulerImpl] SonarQube is stopped
D:\SonarQube\sonarqube-10.2.0.77647\bin\windows-x86-64>
It seems there’s a problem with the Elasticsearch index.
Delete %SONARQUBE_HOME%\data\es8 then start Sonarqube again.
WRT to Elasticsearch, the docs have some recommendations, see
Hey I’m facing the same issue, did you get it resolved? If yes, could you please help me ?
Yes, this was due to the database having crashed and trouble starting it.
Thomas A Gray
MCICOM Installation Support Branch (ISB)
2306 E. Bannister Road
Kansas City, MO 64131-3088
Desk: (816) 705-5109