Please provide
- Operating system: Windows 11
- Visual Studio version: VS 2026 Professional version 18.10.3
- SonarQube for Visual Studio plugin version: 11.0.0.17354
- Programming language you’re coding in: C#
- Is connected mode used: To SonarQube Cloud
And a thorough description of the problem / question:
Visual Studio prompted me to update the extension. Before the update everything - including connected mode - worked fine. Right after the update to version 11.0.0.17354 Visual Studio showed a bar with this text:
The token used for the server connection "<my org> is invalid, please update the credentials.
When I try to enter my access token (which I know is correct and still valid) then I get this error:
The credentials of the connection “<my org>” were not updated: Binding could not be established because Server Connection’s Credentials could not be found. Please check the SonarQube for Visual Studio logs for mor details..
The SonarQube output window shows this:
Summary
Initializing the telemetry package...
Finished initializing the telemetry package...
[Solution Tracking] Initialized with solution solution_name
[Focus on New Code] Focus on New Code definition not available: Configuration scope not initialized
Initializing the notifications package...
Connected: checking for notifications
Finished initializing the notifications package
Initializing the daemon package...
SonarQube for VisualStudio version: 11.0.0.17354
[Connection Migration] The connections.json file already exists. Migrating connections from existing bindings was not performed
Created directory: C:\Users\user_name\AppData\Roaming\SonarLint for Visual Studio\SolutionSettings\solution_name
[Plugin Statuses] Service Provider is unavailable
Current VS version:
Visual Studio Professional 2026
18.10.12224.181
18.10.3
[SLCoreHandler] Creating SLCore instance
[SLCoreHandler] Starting SLCore instance
Loaded settings from "C:\Users\user_name\AppData\Roaming\SonarLint for Visual Studio\settings.json".
Settings file does not exist at "C:\Users\user_name\AppData\Roaming\SonarLint for Visual Studio\SolutionSettings\solution_name\settings.json".
[NodeJSLocator] Checking environment variable SONAR_NODEJS_PATH
[NodeJsLocator] Environment variable is not set
[SLCore > Configuration Scope] Declared Configuration Scope solution_name
[SLCore] Using H2 2.4.240 which is newer than the version Flyway has been verified with. The latest verified version of H2 is 2.3.232.
[SLCore > Configuration Scope] Updated files system parameters for Configuration Scope solution_name: Root=D:\, Commands Directory=D:\Source\repository_name
[solution_name] File 'C:\Program Files (x86)\WiX Toolset v3.14\bin\\WixNetFxExtension.dll' can't be relativized against root 'D:\' and is skipped
[solution_name] File 'C:\Program Files (x86)\WiX Toolset v3.14\bin\\WixUIExtension.dll' can't be relativized against root 'D:\' and is skipped
[solution_name] File 'C:\Program Files (x86)\WiX Toolset v3.14\bin\\WixUtilExtension.dll' can't be relativized against root 'D:\' and is skipped
[solution_name] File 'C:\Users\user_name\AppData\Local\Temp\TFSTemp\vctmp1240_472854.SomeClass.f53ae08e.cs' can't be relativized against root 'D:\' and is skipped
[solution_name] File 'C:\Users\user_name\AppData\Local\Temp\TFSTemp\vctmp14784_122528.SomeClass.22d8e8d7.cs' can't be relativized against root 'D:\' and is skipped
[solution_name] File 'C:\Users\user_name\AppData\Local\Temp\TFSTemp\vctmp18256_46760.SomeClass.ba478c0b.cs' can't be relativized against root 'D:\' and is skipped
[solution_name] File 'C:\Users\user_name\AppData\Local\Temp\TFSTemp\vctmp20668_664451.SomeClass.ba478c0b.cs' can't be relativized against root 'D:\' and is skipped
[solution_name] File 'C:\Users\user_name\AppData\Local\Temp\TFSTemp\vctmp24380_104778.SomeClass.1c7ddf85.cs' can't be relativized against root 'D:\' and is skipped
[solution_name] File 'C:\Users\user_name\AppData\Local\Temp\TFSTemp\vctmp34700_480754.SomeClass.66633aea.cs' can't be relativized against root 'D:\' and is skipped
[solution_name] File 'C:\Users\user_name\AppData\Local\Temp\CopilotBaseline\45d682ae\~SomeClass.cs' can't be relativized against root 'D:\' and is skipped
[solution_name] File 'C:\Users\user_name\AppData\Local\Temp\CopilotBaseline\f949b6eb\~SomeClass.cs' can't be relativized against root 'D:\' and is skipped
[SLCore] No credentials for connection https://sonarcloud.io/organizations/organization_name
Finished initializing the daemon package.
[ConnectedMode/BranchMapping] Matching Sonar server branch: develop
[SLCore > Configuration Scope] Updated analysis readiness for Configuration Scope solution_name: True
Updated analysis readiness: True
[SLCore > Configuration Scope] Updated Sonar branch for Configuration Scope solution_name: develop
Initializing the SonarQube for Visual Studio package...
Finishing initializing the SonarQube for Visual Studio package
[ConnectedMode] Initializing package...
[ConnectedMode] Package initialized
[Taint] Initializing taint issues synchronization package...
[Server Issue Sync > Taint] Fetched 0 taint vulnerabilities.
[Server Issue Sync > Dependency Risks] Fetched 0 dependency risks.
[Taint] Finished initializing taint issues synchronization package.
[Connected Mode > Binding > Manual] The credentials for the connection https://sonarcloud.io/organizations/organization_name could not be found
[SLCore] No credentials for connection https://sonarcloud.io/organizations/organization_name
I’ve even created a new access token and the same problem still happens.
If I open a solution which does not contain a JSON file with binding information, then the error is different. At first it looks like I could update the access token - a success message is shown. But if I later try to select the connection in the bind dialogue, then an error is shown again:
“The token for the selected connection is invalid.”
I can continue this loop forever. Edit connection, enter token, success massage, select connection, error message.
I’ve now downgraded to version 10.9.0.17293 and the first start of VS again showed the "The token used for the server connection “<my org> is invalid” bar. But updating the token worked and now connected mode is working again.