Latest Azure DevOps extension causing error parsing json?

We use your Azure DevOps extension and task which updated to version 4.12 from .11 today.
Since this update we get the following errors on the prepare analysis step in our pipelines.

##[error]Unhandled Exception:

##[error]Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: <. Path ‘’, line 0, position 0.
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at SonarScanner.MSBuild.PreProcessor.SonarWebService.d__10.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at SonarScanner.MSBuild.PreProcessor.TeamBuildPreProcessor.d__12.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at SonarScanner.MSBuild.PreProcessor.TeamBuildPreProcessor.d__11.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at SonarScanner.MSBuild.BootstrapperClass.d__9.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at SonarScanner.MSBuild.BootstrapperClass.d__8.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at SonarScanner.MSBuild.Program.d__4.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at SonarScanner.MSBuild.Program.d__3.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at SonarScanner.MSBuild.Program.d__2.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at SonarScanner.MSBuild.Program.(String args)
##[error]The process ‘F:\agent_work_tasks\SonarQubePrepare_15b84ca1-b62f-4a2a-a403-89b77a063157\4.12.0\classic-sonar-scanner-msbuild\SonarScanner.MSBuild.exe’ failed with exit code 3762504530
Finishing: Prepare analysis on SonarQube

On the service connection side we have version 5.6 of the SonarQube wrapper/scanner (i think)

What can be the cause of this. Was fine yesterday until the extension was updated.

Thank you.

somehow missed this part the actual error:
##[error]Unhandled Exception:

##[error]Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: <. Path ‘’, line 0, position 0.

Hi,

I’m facing the same issues in my Azure DevOps pipeline it was working yesterday with MSbuild 4.1 suddenly stopped with MSbuild 5.0. Any leads on this will be helpful for me too.

Thanks

Hi @Jay_Cooper

Please note that the latest supported version of SonarQube is the 7.9 (LTS).

Mickaël

Hi!

I have the same error with SonarQube Extension 4.20.0 in Azure:
Error: Unexpected character encountered while parsing value: <. Path ‘’, line 0, position 0

Is there any solution?

Thanks in advance.

Mario

Hi @Spanic ,

Welcome to SonarSource Community! :sonarsource:

First, please upgrade to SonarQube 9.0 first. You are using a very old version that may be causing your problems. If you still have issues, please post the entire stack trace and logs here. Please enable debug logs by adding sonar.verbose=true to your Prepare SonarQube Configuration step in the extraProperties key. Please post this in a new thread.