Getting [error]ERROR: { PayloadTooLargeError: request entity too large

SQ Version = 7.9
Azure DevOps Extension version = Latest

We recently upgraded our dotnet project to 6.0 and started seeing this error while running SQ Analysis task.
Note: We are not scanning 3rd party libraries and have installed dotnet 6.0 on build server where azure devops agent is.

##[error]ERROR: { PayloadTooLargeError: request entity too large
ERROR:     at readStream (D:\P1\w\4\s\.scannerwork\css-bundle\node_modules\raw-body\index.js:155:17)
ERROR:     at getRawBody (D:\P1\w\4\s\.scannerwork\css-bundle\node_modules\raw-body\index.js:108:12)
ERROR:     at read (D:\P1\w\4\s\.scannerwork\css-bundle\node_modules\body-parser\lib\read.js:77:3)
ERROR:     at jsonParser (D:\P1\w\4\s\.scannerwork\css-bundle\node_modules\body-parser\lib\types\json.js:135:5)
ERROR:     at Layer.handle [as handle_request] (D:\P1\w\4\s\.scannerwork\css-bundle\node_modules\express\lib\router\layer.js:95:5)
ERROR:     at trim_prefix (D:\P1\w\4\s\.scannerwork\css-bundle\node_modules\express\lib\router\index.js:317:13)
ERROR:     at D:\P1\w\4\s\.scannerwork\css-bundle\node_modules\express\lib\router\index.js:284:7
ERROR:     at Function.process_params (D:\P1\w\4\s\.scannerwork\css-bundle\node_modules\express\lib\router\index.js:335:12)
ERROR:     at next (D:\P1\w\4\s\.scannerwork\css-bundle\node_modules\express\lib\router\index.js:275:10)
ERROR:     at expressInit (D:\P1\w\4\s\.scannerwork\css-bundle\node_modules\express\lib\middleware\init.js:40:5)
ERROR:   message: 'request entity too large',
ERROR:   expected: 146492,
ERROR:   length: 146492,
ERROR:   limit: 102400,
ERROR:   type: 'entity.too.large' }

Any help would be greatly appreciated.


Your version is past EOL. You should upgrade to either the latest version or the current LTS at your earliest convenience. Your upgrade path is:

7.9.* → 8.9.10 → 9.7.1 (last step optional)

You may find the Upgrade Guide and the LTS-to-LTS Upgrade Notes helpful. If you have questions about upgrading, feel free to open a new thread for that here.

Regarding your error, there is likely something on your network, e.g. a proxy, that’s blocking the analysis report submission. You should check with your network folks.