f:\BuildSource\VSTS1\6.sonarqube\bin\targets\SonarQube.Integration.targets(381,5): Error MSB4044: The “GetAnalyzerSettings” task was not given a value for the required parameter “Language”.Process ‘msbuild.exe’ exited with code ‘1’.f:\BuildSource\VSTS1\6.sonarqube\bin\targets\SonarQube.Integration.targets(381,5): Error MSB4044: The “GetAnalyzerSettings” task was not given a value for the required parameter “Language”.Process ‘msbuild.exe’ exited with code ‘1’.

Is there any workaround? We started noticing this error message on 2018/10/12.

Same problem, first noticed on 12/10/2018.
Unfortunately @quintush work around is not viable, as that would mean editing 30+ dcproj files, pull requests, approvals, etc etc. to work around a problem that did not exist a week ago.
Is there a fix planned by Sonarcloud. Or will this remain as expected behaviour and require customers to make dev changes to resolve?
Is anyone aware of a workaround that can be done in the build definition, this would be fine as it means 1 change in a task group common to all project build.

Since we are using Azure devops and not annotating any SonarQube specific code in our .NET solution the provided workaround is not valid for us. What would also help is to specify a specific version of SonarQube to use instead of the latest 4.x version from wihin our build pipeline.
It broke our pipeline and our build agent, since it left the agent in an inconsistent state (all kind of SonarQube dll’s were not cleaned, resulting in even more errors).
To fix the agent, we had to move the “Run code analysis” task before the build, so that it could fail gracefully and clean up all the SonarQube dependencies. Hopefully this helps anyone.

Here’s a powershell script I wrote to automatically implement @quintush’s fix on all deployproj files in the Azure DevOps sources directory. I have it running towards the start of the build, before the SonarQube “prepare analysis” step.

@all, the issue is being tracked by Scanner for MSBuild issue #589. We’ve released new versions of the scanner and the VSTS tasks to address the issue. Please let us know if you are still experiencing problems.
Please accept our apologies for the inconvenience.

Root cause: a property in one of our custom MSBuild tasks was marked as Required in version 4.4.1. The Scanner for MSBuild is embedded in the Azure DevOps SonarCloud and SonarQube extensions, which were re-released on Friday. The new versions of the extensions were minor updates, so they would have been automatically deployed by the build agents the next time a build using the task was executed.