versions used (SonarQube, Scanner, Plugin, and any relevant extension)
SonarQube 9.0.1 community Edition
error observed (wrap logs/code around triple quote ``` for proper formatting) Installed 9.0.1 community Edition using “Start Sonar” , but unable to create service using “startNTservice” . Getting an error “The SonarQube service is not installed - The specified service does not exist as an installed service. (0x424) Press any key to continue”. We are using Windows2019 OS
steps to reproduce : NA
potential workaround : Nothing
P.S.: use the #bug:fault sub-category if you’re hitting a specific crash/error , or the #bug:fp sub-category for rules-related behaviour
Hi Tobias, Thanks now able to create service.
We are getting “Cant reach this page” do we need to do any other settings.
Configured details in “Sonar” and “Wrapper” files.
Attached logs, Showing error “Unable to start Database”
Actually i am doing this in lower environment, so just checking first with out DB connections. Can i use existing Dev environment SonarQube Enterprise 8.9 version to test this. If this works i will create dedicated DB.
Attached log fileweb.log (46.9 KB)
okay so just to clarify you already know how to handle this error and will create a dedicated db for your environment?
else i will highlight the obvious that you probably copied a h2 database from somewhere or provided jdbc username/password properties where none should be.
let me know how it will go with a dedicated database
I am doing this Community Edition first time, earlier another engineer worked in this SQ install. At least with out DB connection we should get home page right even that I am not getting while accessing with port and localhost. We should get SQ homepage right?
I am requesting new DB instance for this and will use that DB connection, do we need any pre requisites for DB instance.
Hi Tobias,
Created new DB and connected with SQ DB.
But when we are accessing the home page with url:http://localhost:9000/ its keep on loading and not getting home page. Could you help in this…log and homepage screen attached.
the logs look clean. could you try to clean the cache or check if you have a webcontext defined in the properties? SQ should be operational judging from the logs (btw no need to increase the log level for now).