Run Code Analysis unable to upload the analysis report to Sonarqube server

SonarQube Server / Community Build
1

  • which versions are you using - Enterprise Edition Version 9.9.3 (build 79811)

  • how is SonarQube deployed: On premise server (zip)

  • what are you trying to achieve - We are achieving to run sonar analysis for Azure devops project using azure devops pipelines

  • what have you tried so far to achieve this - We have tried to increase the limit of files using sonar.filesize.limit=25 in sonar-project.properties files

We are getting below error for one branch only:

INFO 748/749 source files have been analyzed

INFO Analysis report generated in 1556ms, dir size=53.2 MB
INFO Analysis report compressed in 7543ms, zip size=20.3 MB
INFO Time spent writing ucfgs 3889ms
INFO EXECUTION FAILURE

##[error]07:24:05.041 ERROR Error during SonarScanner CLI execution
java.lang.IllegalStateException: Failed to upload report: Fail to request url: https://pumasonarqube.cloud.coolfurnace.net/api/ce/submit?projectKey=Salesforce&projectName=Salesforce

2

Hey there.

This issue typically indicates a communication problem between the scanner and your SonarQube server— often related to the proxy handling HTTPS traffic for your SonarQube instance.

First, you should check the relevant server logs, paying particular attention to the access.log. Look for any sign of the failing request from the scanner. - If you find entries for the problematic request, there may be an issue with the SonarQube server configuration.

If there are no such entries, this indicates the request never reached the SonarQube server, and the issue likely lies elsewhere.

That’s when it makes sense to examine the logs of your proxy. Common issues include a maximum request size being exceeded.

sonar.filesize.limit is not relevant here.

:warning: Your version is past EOL. You should upgrade to either the latest version or the current LTA (long-term active version) at your earliest convenience. Your upgrade path is:

9..9 → 2025.1.1-> 2025.2 (last step optional)

You may find these resources helpful:

If you have questions about upgrading, feel free to open a new thread for that here.

3

Hi Colin,

Thanks for your reply!!

We have checked logs, there is isn’t such issue,
To increase the max request size we have done below configuaration in IIS settings:

  • changed maxRequestEntityAllowed to 300000000
  • changed uploadReadAheadSize to its maximum allowed value.
  • Set maxAllowedContentLength to its maximum value 4294967295

After doing above configuaration also it is failing

This issue is only for particular branch/commit, other branches for other projects are completely working fine.

Thank you

4

Hi there,

Thanks for the update.

To help narrow down where the issue is occurring, I encourage you to check where the failing request is reaching—whether it’s making it to the proxy (IIS) or all the way through to the SonarQube server itself. You can do this by examining the access logs for both IIS and SonarQube around the time of the failed request.

  • If you see the request in the SonarQube server logs, the request is getting through IIS, and the problem likely lies with SonarQube’s handling of that request/branch. We would have to investigate further.
  • If it only appears in the IIS logs but not on the SonarQube side, IIS may still be blocking or modifying it (even with increased limits).
  • If it doesn’t reach either, there may be a client-side or network issue.

Let me know what you find in the logs!

5

Hi Colin,

Thanks for your prompt reply

We have checked logs we are not getting any clue what is wrong.

And the thing is we have run the same pipeline for same branch for another sonarqube instance running on different server, this is completely working fine.

The error now we are getting is below:
##[error]14:32:33.702 ERROR Error during SonarScanner CLI execution
java.lang.IllegalStateException: Failed to upload report: Error 413 on https://pumasonarqube.cloud.coolfurnace.net/api/ce/submit?projectKey=SFDC&projectName=SFDC&characteristic=branch%3DDCT_Test_Benin&characteristic=branchType%3DBRANCH : Payload Too Large

We have 3 enterprise licenses(1 for Prod and 2 for NonProd) for Sonarqube, can you please arrange a call with your technical support team, so that we can show and explain you a issue in screen-sharing mode, infact which will be more convenient!!

Thanks and Regards,
Manjunath S A

6

If you’re getting a 413 error from IIS, you probably want to increase uploadReadAheadSize. That said, we aren’t IIS experts! SonarQube will under no circumstances return a 413 – that’s all IIS.

You’re welcome to get in touch with Commercial Support if you have access (purchased as part of your license), but otherwise we’ll keep it here in the Community. :slight_smile: