Need urgent help with Integration of Sonarqube 8.6 with postgreSQL 12 in windows 10

Using sonarqube 8.6
*Iam trying to integrate Sonarqube with postgres database on windows 10 with pgadmin .
*I did not install the softwares but I have extracted the zip files of sonarqube 8.6, and Java version 11, pgadmin 12, windows 10 as the OS as I don’t have the admin access.

I have changed the sonar/config.properties and added path of java 11 to it and also jdbc driver for postgreSQL.
When I am trying to start the Sonarqube , It is detecting java 11 but still giving an error in starting the sonarqube.
This below logs are from command prompt:

C:\softwares\sonarqube-8.6.1.40680\bin\windows-x86-64>StartSonar
wrapper  | --> Wrapper Started as Console
wrapper  | Launching a JVM...
jvm 1    | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
jvm 1    |   Copyright 1999-2006 Tanuki Software, Inc.  All Rights Reserved.
jvm 1    |
jvm 1    | 2023.01.30 14:20:34 INFO  app[][o.s.a.AppFileSystem] Cleaning or creating temp directory C:\softwares\sonarqube-8.6.1.40680\temp
jvm 1    | 2023.01.30 14:20:34 INFO  app[][o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:59068]
jvm 1    | 2023.01.30 14:20:34 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [C:\softwares\sonarqube-8.6.1.40680\elasticsearch]: C:\softwares\java11\java11\jdk11.0.10_9\bin\java -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -Djava.io.tmpdir=C:\softwares\sonarqube-8.6.1.40680\temp -XX:ErrorFile=../logs/es_hs_err_pid%p.log -Des.networkaddress.cache.ttl=60 -Des.networkaddress.cache.negative.ttl=10 -XX:+AlwaysPreTouch -Xss1m -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djna.nosys=true -XX:-OmitStackTraceInFastThrow -Dio.netty.noUnsafe=true -Dio.netty.noKeySetOptimization=true -Dio.netty.recycler.maxCapacityPerThread=0 -Dio.netty.allocator.numDirectArenas=0 -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -Djava.locale.providers=COMPAT -Des.enforce.bootstrap.checks=true -Xmx512m -Xms512m -XX:MaxDirectMemorySize=256m -XX:+HeapDumpOnOutOfMemoryError -Delasticsearch -Des.path.home=C:\softwares\sonarqube-8.6.1.40680\elasticsearch -Des.path.conf=C:\softwares\sonarqube-8.6.1.40680\temp\conf\es -cp lib/* org.elasticsearch.bootstrap.Elasticsearch
jvm 1    | 2023.01.30 14:20:34 INFO  app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
jvm 1    | OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
jvm 1    | 2023.01.30 14:20:41 INFO  app[][o.s.a.SchedulerImpl] Process[es] is up
jvm 1    | 2023.01.30 14:20:41 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[[key='web', ipcIndex=2, logFilenamePrefix=web]] from [C:\softwares\sonarqube-8.6.1.40680]: C:\softwares\java11\java11\jdk11.0.10_9\bin\java -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djava.io.tmpdir=C:\softwares\sonarqube-8.6.1.40680\temp -XX:-OmitStackTraceInFastThrow --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED -Xmx1024m -XX:MaxPermSize=256m -XX:+HeapDumpOnOutOfMemoryError -Dhttp.nonProxyHosts=localhost|127.*|[::1] -cp ./lib/common/*;C:\softwares\sonarqube-8.6.1.40680\lib\jdbc\postgresql\postgresql-42.2.17.jar org.sonar.server.app.WebServer C:\softwares\sonarqube-8.6.1.40680\temp\sq-process1348130412182804233properties
jvm 1    | OpenJDK 64-Bit Server VM warning: Ignoring option MaxPermSize; support was removed in 8.0
jvm 1    | 2023.01.30 14:20:43 INFO  app[][o.s.a.SchedulerImpl] Process[web] is stopped
jvm 1    | 2023.01.30 14:20:43 INFO  app[][o.s.a.SchedulerImpl] Process[es] is stopped
jvm 1    | 2023.01.30 14:20:43 INFO  app[][o.s.a.SchedulerImpl] SonarQube is stopped
wrapper  | <-- Wrapper Stopped

Hey there.

At a minimum, you should be using SonarQube v8.9 LTS (any earlier version is EOL).

If you have trouble starting a supported version of SonarQube – check the logs!

Take note that sonar/config.properties is not a valid file to be used for configuring SonarQube, nor should you need to configure a PostgreSQL driver. Any configuration files can be found under the conf/ directory of your SonarQube installation directory.