ERROR: Project not found. Please check the 'sonar.projectKey' and 'sonar.organization' properties, t

[anderson.silva (Anderson Sebastiao da Silva)]

Can you please help us with the error below?

ERROR: Project not found. Please check the ‘sonar.projectKey’ and ‘sonar.organization’ properties, the ‘SONAR_TOKEN’ environment variable, or contact the project administrator

ERROR: Error during SonarScanner execution
log-sonar-prepare.txt (13.8 KB)
log-sonar.txt (99.2 KB)
The strange thing is that if we create a new one, a project with another name works.
Good Morning.

I’m attaching run logs to help with analyses.

[anderson.silva (Anderson Sebastiao da Silva)]

Good afternoon.
Can you please help me with a problem with Sonar Cloud.
When trying to analyze a project it returns the message that the project does not exist (ERROR: Project not found.). But the project exists in my database. The contour we used to rename the current project and rotate the pipe again to create a new project.

Has anyone gone through this problem?

Grateful.
Anderson.

[ganncamp (G Ann Campbell)]

Hi Anderson,

Are you using SonarQube or SonarCloud?

Could you provide the full analysis log?

The analysis / scanner log is what’s output from the analysis command. Hopefully, the log you provide will include that command as well.

This guide will help you find them.

 
Ann

[anderson.silva (Anderson Sebastiao da Silva)]

Hi Ann,

I use SonaCloud for code analysis.
log-sonar-prepare.txt (13.8 KB)
log-sonar.txt (99.2 KB)

I have attached the logs from that post.

[ganncamp (G Ann Campbell)]

Hi,

Thanks for the logs. More fully, the error you’re getting is this:

ERROR: Project not found. Please check the 'sonar.projectKey' and 'sonar.organization' properties, the 'SONAR_TOKEN' environment variable, or contact the project administrator

Earlier in the log, I see this:

2022-11-09T21:20:20.7747181Z ##[debug]SONARQUBE_SCANNER_PARAMS={"sonar.host.url":"https://sonarcloud.io/","sonar.login":***,"sonar.organization":"aab440a34d90e639a6858a99eb4f0656f8e14fc5","sonar.projectKey":"SN.API.PortalLojista"...

And then later, this:

2022-11-09T21:20:39.1536779Z INFO: Load project settings for component key: 'SN.API.PortalLojista'
2022-11-09T21:20:46.3105905Z INFO: Load project settings for component key: 'SN.API.PortalLojista' (done) | time=7154ms

So it’s seems that your organization key and project key are provided and correct (even though that hex organization key looks odd to me).

So let’s come back to the error message:

`Please check … the ‘SONAR_TOKEN’ environment variable,

You’re passing a sonar.login property, presumably with your analysis token. But analysis is expecting that value as an env var.

 
HTH,
Ann

[Jane]

Hi Ann. Thanks for your response. We have 800 pipelines that use the same template. The same token is used in all the pipelines. Apparently on november 8th the Sonar analysis task started to throw this error. It worked in the morning, and in the afternoon, we started to get the error. We have around 10 projects with the same problem for now. The rest is working fine. But the problem seems to be spreading and everyday we see a new repo with the problem.

We use azure devops tasks. This task is configured with a SonarCloud Connection in which we insert the token.

[ganncamp (G Ann Campbell)]

Hi,

Thanks for the followup. I’ve pinged the team internally.

 
Ann

[ganncamp (G Ann Campbell)]

Hello,

I just realized you created two threads for the same problem.

Please don’t do that. Do feel free though to ping on an existing thread if after 3+ days you begin to feel it’s been overlooked. I’m going to combine your two threads.

 
Ann

[Serhat_Yenican]

Hello,

I checked the logs and noticed that your SONAR_TOKEN belongs to a user who doesn’t have the necessary permission to submit the analysis report. The ‘Execute Analysis’ permission is required for this. Please note that you may also need the ‘Browse’ permission to request the quality status. These permissions can be given to a user at the organization or project level.