We are trying to use this Community Build 25.9.0 version which we are frequently facing 500 error -
00:00:12 Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'ProjectConfiguration' defined in org.sonar.scanner.scan.ProjectConfigurationProvider: Unsatisfied dependency expressed through method 'provide' parameter 3: Error creating bean with name 'ProjectServerSettings' defined in org.sonar.scanner.scan.ProjectServerSettingsProvider: Failed to instantiate \[org.sonar.scanner.scan.ProjectServerSettings\]: Factory method 'provide' threw exception with message: Error 500 on http://172.16.24.75:9002/api/settings/values.protobuf?component=loadtest3 : {"errors":\[{"msg":"An error has occurred. Please contact your administrator"}\]}
Hi,
Welcome to the community!
Only the latest version of SonarQube Community Build is considered active, so you’ll need to update and see if the situation is still replicable before we can help you.
Your update path is:
25.9 → 26.1
You may find these resources helpful:
- Update Guide
- SonarQube Community Build Update Notes (all update notes since the switch)
If you have questions about upgrading, feel free to open a new thread for that here.
That said, the error you’re seeing is a 500 error:
You should check your server logs/
HTH,
Ann
Hi Ann,
Let me explain you my issue.
We migrated from SonarQube Community Edition 10.4.1 (Oracle) to the latest Community Build (v25.x) on Postgres to resolve scan slowness. However, we encountered persistent HTTP 500 errors during via Jenkins source code scans when attempting to download quality profiles and start scanning.
Despite testing across both Postgres and Oracle, and even reverting to the stable 10.7.0 release, the 500 error remains. We are seeking the root cause and permanent configuration tuning to stabilize the scanning process.
org.sonar.scanner.report.ActiveRulesPublisher': Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ActiveRules' defined in org.sonar.scanner.rule.ActiveRulesProvider: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate \[org.sonar.api.batch.rule.internal.DefaultActiveRules\]: Factory method 'provide' threw exception; nested exception is org.sonarqube.ws.client.HttpException: Error 500 on [http://172.16.24.75:9002/api/rules/list.protobuf?qprofile=e20ad98f-2e5f-4708-a8d4-1d278ab7e30e&ps=500&p=1](http://172.16.24.75:9002/api/rules/list.protobuf?qprofile=e20ad98f-2e5f-4708-a8d4-1d278ab7e30e&ps=500&p=1) : {"errors":\[{"msg":"An error has occurred. Please contact your administrator"}\]}
2)Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate \[org.sonar.api.batch.rule.internal.DefaultActiveRules\]: Factory method 'provide' threw exception; nested exception is org.sonarqube.ws.client.HttpException: Error 500 on http://172.16.24.75:9002/api/rules/list.protobuf?qprofile=230c5c79-c442-4680-9395-79c2cd01bc30&ps=500&p=1 : {"errors":\[{"msg":"An error has occurred. Please contact your administrator"}\]}
03:02:42 Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate \[org.sonar.api.batch.rule.internal.DefaultActiveRules\]: Factory method 'provide' threw exception; nested exception is org.sonarqube.ws.client.HttpException: Error 500 on [http://172.16.24.75:9002/api/rules/list.protobuf?qprofile=b6ddeabf-f4e6-4126-9d28-9132e4a1f288&ps=500&p=1](http://172.16.24.75:9002/api/rules/list.protobuf?qprofile=b6ddeabf-f4e6-4126-9d28-9132e4a1f288&ps=500&p=1) : {"errors":\[{"msg":"An error has occurred. Please contact your administrator"}\]}
Thank we were tr
web.log (719.8 KB)
ce.log (654.3 KB)
es.2026-01-31.log (248 Bytes)
es.2026-02-01.log (252 Bytes)
sonar.log (3.7 KB)
es.log (125 Bytes)
web.2026-01-31.log (41.1 KB)
web.2026-02-01.log (199.2 KB)
web.2026-02-02.log (244 Bytes)
web.2026-02-03.log (67.4 KB)
i have uploaded logs here . could you plz suggest and help us to proceed further ASAP
Hi,
Your es.log file sizes are measured in bytes and I can’t read your web.log files. It looks like the encoding is off. Can you read them and see if there are any errors in them?
Ann
Hi again,
One of my colleagues was open your web.log files. It looks like your database might be corrupted. You should restore your backup and run the update again.
HTH,
Ann