SonarCloud - VSTS - MSBuild now failing


(Peter Connor) #1


Within the last couple of hours the running of code analysis step in my VSTS build is now breaking my build. Has anything changed your end?

Earlier this morning and previously, I would get a error message regarding one of our CSS files:
“ERROR: Failed to parse file:///xxxxx.css”
the build would just continue fine and go through ignoring that file.

Now, I am getting the following error:

ERROR: Error during SonarQube Scanner execution
ERROR: An error occured while deserializing UCFG for method
ERROR: Caused by: Protocol message had invalid UTF-8.

The build then breaks at this step and doesn’t go any further…

The weird thing is if I run previously successful builds again now, they begin to error too.

Any help would be much appreciated.


(Nicolas Bontoux) #2

Hi Pete,

Are you using SonarQube or SonarCloud ? If former, any recent change in the setup (version, plugins installed) ? If latter, are these open-source project that you can share links to ? Any additional context/log would be helpful in narrowing this down.

(Peter Connor) #3


I am using SonarCloud and I am afraid they are private projects.

Judging by this thread just posted too though it looks like it might be something released your end:


An error occured while deserializing UCFG for method
(Mr Beanzy) #4

Hi Peter, looks like we hit on the same issue, ours started failing shortly after that was changed. Could be a coincidence. But the code has changed around UCFG and thats the error we get. Unfortunately our projects are private so i cant share them. But nothing has changed in terms of build pipeline

(Amaury Levé) #5

Hi @pconnor,

There was a wrong deployment of one of the product which causes this issue. The product is being rollbacked as we speak and your next analysis should be alright.

Sorry for the inconvenience caused by that.


(Mr Beanzy) #6

Thank you for the confirmation

(Peter Connor) #7

Ok, thank you for the quick response, I will give it an hour and then try again.


(Fabrice Bellingard) #8

Hi guys, problem is now fixed. Sorry for the inconvenience!

(Peter Connor) #9

Builds are running through fine again now.

Thank you :smiley: