Sonar build plugins don't find the projects rules anymore

we are using

  • Sonarqube Community Edition Version 8.9.9 (build 56886)

Our CI fails since yesterday with this error message.

Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin: (default-cli) on project com.exoknox.fdm.parent: Unable to load component class Unable to load component class org.sonar.api.batch.rule.internal.DefaultActiveRules: Error 404 on,name,severity,lang,internalKey,templateKey,params,actives,createdAt,updatedAt,deprecatedKeys&activation=true&qprofile=AXGjZQvs72Ga61OKbGb8&ps=500&p=1 : {“errors”:[{“msg”:“The specified qualityProfile \u0027AXGjZQvs72Ga61OKbGb8\u0027 does not exist”}]} → [Help 1]

found that the profile the projects are using (Sonar Way Java) seems not to have the id AXGjZQvs72Ga61OKbGb8 but AWNfKIjmUMoe9cI1im-1. I don’t know where the wrong Id comes from. We didn’t change anything with regards to the sonar configuration neither in the build nor on the projects in sonarQube.

Any help will be much appreciated.


Is this ‘Sonar Way Java’ profile a build-in profile or a custom one created by your organization?

And is it the default profile, or one that your project is assigned to explicitly?



It is the built-in profile and also the default one.



Could you try:

  • stop the server
  • delete $SONARQUBE-HOME/data/es7
  • start the server (& wait for the Elasticsearch indices to rebuild)
  • reanalyze



Hi, Thanks
We have done that without success - but we figured out that our postgres database has duplicate entries . we cleaned it up and upgrated to version 12 - at the end after clearing es indices again and restarting finally we went back to normal :slight_smile:

1 Like