Error Binding VS 2017 Solution: Failed to Write Credentials

SonarQube for IDE Visual Studio
,
1

I’m able to connect to my SonarQube server through the VS2017 Team Explorer with my personal cred’s and a token. When the solution starts binding though it fails with this error.

Updating binding…
Binding solution to SonarQube project: Started
Binding solution to SonarQube project: Discovering solution projects
Included projects:

  • removed list for security
    Excluded projects:
  • removed list for security
    You can change the exclusion options via the SonarLint project-level context menu i.e. Solution Explorer → Select project(s)
    Binding solution to SonarQube project: Download quality profile(s):
    Successfully downloaded quality profile. Name: ‘DotNet COE Standard’, Key: ‘******’, Language: ‘C#’
    INFO: SonarLint connected mode no longer installs the analyzers NuGet packages. The analyzers embedded in the VSIX are used instead.
    Binding solution to SonarQube project: Generating project rule sets
    Unexpected error during workflow execution: Failed to write credentials.

SonarLint Version: 4.6.0.3815

4

Thanks for reporting the issue, and apologies for the very long delay.

FYI I’ve created SLVS-1209 to track this issue. Unfortunately, we haven’t managed to reproduce it locally. Is it still an issue for you locally?

5

I don’t think this is a problem anymore. VS2019 seems to bind just fine last time I used it.

1 Like
6

Thanks for the update @Alex_Jamrozek.

I’ll keep the bug open for a while, then close it if no-one else reports an issue.

7

Same error, VS2019 16.4.6.

I get one additional line before the “Failed to write credentials” error.
“Ruleset binding: all projects need to be updated reference the generated ruleset.”

Every time the binding tries to run, an additional ruleset file is added to every project.

I had just deleted the .sonarlint and .sonarqube folders, etc as recommended https://groups.google.com/forum/#!topic/sonarlint/_hgsvV6WHEU because I am trying to switch from a localhost sonarqube to our corporate one. (build pipeline issues were preventing project creation on the server)