# ERROR: Analysis didn't terminate normally, please verify ERROR and WARN logs above. Exit code 1 **URL:** \ **Category:** SonarQube Cloud\ **Tags:** css, azuredevops-services\ **Created:** [June 27, 2019, 4:18pm UTC](https://community.sonarsource.com/t/error-analysis-didnt-terminate-normally-please-verify-error-and-warn-logs-above-exit-code-1/11307 "2019-06-27T16:18:33Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![bouke](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/bouke/32/1947_2.png) [@bouke](https://community.sonarsource.com/u/bouke)\ **Post date:** [June 27, 2019, 4:18pm UTC](https://community.sonarsource.com/t/error-analysis-didnt-terminate-normally-please-verify-error-and-warn-logs-above-exit-code-1/11307/1 "2019-06-27T16:18:33Z")
Since a few days I’m getting the following error in my builds. I’m using sonarsource in an Azure DevOps (formerly VSTS) build pipeline. The error doesn’t seem to prevent the analysis from completing, but it does cause unnecessary clutter. Why is this happening, and what can I do about it? ```auto ##[section]Starting: Run code analysis ============================================================================== Task : Run Code Analysis Description : Run scanner and upload the results to the SonarCloud server. Version : 1.6.3 Author : sonarsource Help : This task is not needed for Maven and Gradle projects since the scanner should be run as part of the build. [More Information](http://redirect.sonarsource.com/doc/install-configure-scanner-tfs-ts.html) ============================================================================== [command]C:\VSTS\_work\_tasks\SonarCloudPrepare_14d9cde6-c1da-4d55-aa01-2965cd301255\1.6.3\classic-sonar-scanner-msbuild\SonarScanner.MSBuild.exe end SonarScanner for MSBuild 4.6.2 Using the .NET Framework version of the Scanner for MSBuild Post-processing started. ... INFO: Sensor SonarCSS Metrics [cssfamily] INFO: Sensor SonarCSS Metrics [cssfamily] (done) | time=256ms INFO: Sensor SonarCSS Rules [cssfamily] INFO: Sensor SonarCSS Rules [cssfamily] (done) | time=5759ms INFO: Sensor C# Properties [csharp] ERROR: Analysis didn't terminate normally, please verify ERROR and WARN logs above. Exit code 1 ``` Note that although the message says to verify ERROR and WARN logs, there aren’t any. Only loads of INFO logs. ---
**Author:** ![SamSmithNZ](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/samsmithnz/32/4859_2.png) [@SamSmithNZ](https://community.sonarsource.com/u/SamSmithNZ)\ **Post date:** [June 28, 2019, 3:14pm UTC](https://community.sonarsource.com/t/error-analysis-didnt-terminate-normally-please-verify-error-and-warn-logs-above-exit-code-1/11307/2 "2019-06-28T15:14:14Z")
I second this, I’ve noticed the same thing this week and would like to understand why… ---
**Author:** ![Godin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/godin/32/122_2.png) [@Godin](https://community.sonarsource.com/u/Godin)\ **Post date:** [June 29, 2019, 11:53pm UTC](https://community.sonarsource.com/t/error-analysis-didnt-terminate-normally-please-verify-error-and-warn-logs-above-exit-code-1/11307/4 "2019-06-29T23:53:09Z")
> [@bouke](#): > > Why is this happening See [Exclude JS/TS from analysis by vilchik-elena · Pull Request #188 · SonarSource/sonar-css · GitHub](https://github.com/SonarSource/sonar-css/pull/188) > [@bouke](#): > > what can I do about it? Instead of `1.1.0` use version `1.1.1` of sonar-css-plugin that contains above change. ---
**Author:** ![SamSmithNZ](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/samsmithnz/32/4859_2.png) [@SamSmithNZ](https://community.sonarsource.com/u/SamSmithNZ)\ **Post date:** [June 30, 2019, 12:33am UTC](https://community.sonarsource.com/t/error-analysis-didnt-terminate-normally-please-verify-error-and-warn-logs-above-exit-code-1/11307/5 "2019-06-30T00:33:27Z")
We are using Azure DevOps, which pulls in the latest 1.\* version. but this doesn’t match up with your version. As you can see above, it still, as of right now, appears to be using version 1.6.3… ---
**Author:** ![mickaelcaro](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/mickaelcaro/32/4147_2.png) [@mickaelcaro](https://community.sonarsource.com/u/mickaelcaro)\ **Post date:** [July 1, 2019, 6:39am UTC](https://community.sonarsource.com/t/error-analysis-didnt-terminate-normally-please-verify-error-and-warn-logs-above-exit-code-1/11307/6 "2019-07-01T06:39:19Z")
Hi, There will be no need to upgrade the extension itself, the plugin will be upgraded today on SonarCloud side, thus will be fixed by then. Sorry for the inconvenience. Mickaël ---
**Author:** ![Godin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/godin/32/122_2.png) [@Godin](https://community.sonarsource.com/u/Godin)\ **Post date:** [July 1, 2019, 9:43am UTC](https://community.sonarsource.com/t/error-analysis-didnt-terminate-normally-please-verify-error-and-warn-logs-above-exit-code-1/11307/7 "2019-07-01T09:43:05Z")
@SamSmithNZ `1.6.3` is the version of Azure DevOps extension, not of `sonar-css-plugin`. My previous comment applies for on-premise SonarQube, in case of SonarCloud as @mickaelcaro said - plugin will be updated today. ---
**Author:** ![simon.brandhof](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/simon.brandhof/32/33_2.png) [@simon.brandhof](https://community.sonarsource.com/u/simon.brandhof)\ **Post date:** [July 1, 2019, 7:24pm UTC](https://community.sonarsource.com/t/error-analysis-didnt-terminate-normally-please-verify-error-and-warn-logs-above-exit-code-1/11307/8 "2019-07-01T19:24:51Z")
@bouke I confirm that the fix has been deployed. Sorry for the inconvenience.