Issues no longer appear in IDE

Kennet · March 28, 2025, 1:43pm

Hi

My information

Operating system: Windows 11
Visual Studio version: Microsoft Visual Studio Professional 2022 (64-bit) Version 17.13.5
SonarQube for Visual Studio plugin version: 8.14.0.12562
Programming language you’re coding in: C++
Is connected mode used: Yes
- SonarQube Server: v2025.1.1 (104738)

SonarLint in Visual studio does not show any SonarQube issues.
I tried creating a empty project and this is what the log shows:

Initializing the telemetry package...
Finished initializing the telemetry package...
Initializing the daemon package...
[Connection Migration] The connections.json file already exists. Migrating connections from existing bindings was not performed
Current VS version:
    Visual Studio Professional 2022
    17.13.35919.96
    17.13.5
[SLCoreHandler] Creating SLCore instance
[SLCoreHandler] Starting SLCore instance
Settings file does not exist at "C:\Users\kniels\AppData\Roaming\SonarLint for Visual Studio\settings.json".
Default settings will be used
[NodeJSLocator] Checking environment variable SONAR_NODEJS_PATH
[NodeJsLocator] Environment variable is not set
Finished initializing the daemon package.
[SLCore] Can't open directory channel. Log directory fsync won't be performed.
Solution/folder is not in a git repository
[Connected Mode > Shared Binding] The shared binding configuration file was not found and will not be used. Probed path: not found
Updated analysis readiness: True
[SLCoreAnalyzer] Analyzing C:\Users\kniels\source\repos\Testing\ConsoleApplication3\ConsoleApplication3\main.cpp with id ff2da8c4-f657-4339-b38c-286c5171b1bf
Initializing the notifications package...
Not connected: not checking for notifications
Finished initializing the notifications package
[Connected Mode > Shared Binding] The shared binding configuration file was not found and will not be used. Probed path: not found
"ClCompilerPath" was not found.
"CLToolExe" was not found, falling back to cl.exe.
C:\Program Files\BullseyeCoverage\bin\cl.exe
[CFamily Analysis] Error retrieving VCX configuration. File: C:\Users\kniels\source\repos\Testing\ConsoleApplication3\ConsoleApplication3\main.cpp, Error: Microsoft.VisualStudio.ProjectSystem.ProjectException: The "CL" rule is missing the "PrecompiledHeader" property.
   at Microsoft.VisualStudio.ProjectSystem.ProjectErrorUtilities.ThrowProjectExceptionHelper(Exception innerException, String unformattedMessage, Object[] args)
   at Microsoft.VisualStudio.ProjectSystem.ProjectErrorUtilities.ThrowProjectException(String message, Object arg0, Object arg1)
   at Microsoft.VisualStudio.ProjectSystem.ProjectErrorUtilities.ThrowRulePropertyMissing(ConfiguredProject configuredProject, String ruleName, String propertyName, String fileName, String itemType, String itemName)
   at Microsoft.VisualStudio.Project.VisualC.VCProjectEngine.VCRulePropertyStorage.<>c__DisplayClass5_0.<<GetEvaluatedPropertyValue>b__0>d.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 Microsoft.VisualStudio.Project.VisualC.VCProjectEngine.ApartmentMarshaler.<>c__DisplayClass9_0`1.<<Invoke>b__0>d.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 Microsoft.VisualStudio.Threading.JoinableTask.CompleteOnCurrentThread()
   at Microsoft.VisualStudio.Threading.JoinableTask`1.CompleteOnCurrentThread()
   at SonarLint.VisualStudio.Integration.Vsix.CFamily.VcxProject.CmdBuilder.AddOptFromProperties(IVCRulePropertyStorage properties)
   at SonarLint.VisualStudio.Integration.Vsix.CFamily.VcxProject.FileConfig.TryGet(ILogger logger, ProjectItem dteProjectItem, String absoluteFilePath, IFileSystem fileSystem)
   at SonarLint.VisualStudio.Integration.Vsix.CFamily.VcxProject.FileConfigProvider.GetInternal(String analyzedFilePath, DTE2 dte)
[SLCoreAnalyzer] No compilation database found for file: C:\Users\kniels\source\repos\Testing\ConsoleApplication3\ConsoleApplication3\main.cpp. Check that the file is part of a supported project type in the current solution.
[SLCore] Node.js could not be automatically detected, has to be configured manually in the SonarLint preferences!
[SLCore] Failed to recover to valid root, address = 42907710, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42859235, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42810368, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42758403, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42702700, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42643539, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42581632, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42513832, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42498416, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42480532, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42464491, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42448450, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42432409, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42406807, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42386035, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42316704, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42296480, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42275797, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42206321, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42185484, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42162177, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42091800, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42064695, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42044448, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42022893, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42003099, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 41983305, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 41960620, file = 00000001800.xd
[SLCore] Unexpected error occurred in scheduled task
[SLCoreAnalyzer] Finished analyzing C:\Users\kniels\source\repos\Testing\ConsoleApplication3\ConsoleApplication3\main.cpp with id ff2da8c4-f657-4339-b38c-286c5171b1bf, analysis time: 3,243s

So It looks like it is analyzing something just not showing anything.
I have tried removed the entire TFSTemp and .sonarlint folders.

/Kennet

georgii.borovinskikh · March 31, 2025, 11:05am

Hi @Kennet

SonarQube for IDE can execute multiple analyzers per file. A typical scenario for a C/C++ file would be C/C++ analysis + secrets analysis. You may see that analysis is executed without any results because we still execute it even if one of the languages is missing the necessary configuration.

In your particular case there’s a problem with getting the file/project properties from your vcxproj, which are needed by our C/C++ analyzer to run properly.

Does this happen only for this project? Do other C/C++ files from other projects in your current solution get analyzed correctly? Do you have other C/C++ solutions, does analysis work there?

One way to test it is to add a simple //todo comment somewhere in your code, which should raise an issue on that line.

If it is something that only happens for this particular project, could you please provide the source code to us for debugging purposes?

Kennet · March 31, 2025, 11:31am

Hi

Thanks for you reply.

No

I only have one project in the solution. So not sure but I guess it would be the same.

No, I have tried with different solutions.

If I just create a new “hello world” windows console application I am not getting any warnings after adding this c++ code:

int main()
{
    std::cout << "Hello World!\n";

    //TODO: testing
    new char[100];
    /*
    int y = 0;
    */
}

georgii.borovinskikh · March 31, 2025, 1:01pm

I can’t reproduce the problem. Judging by the fact that the analysis is not working for all solutions on your PC, it seems to be a problem with compiler/IDE configuration.

Could you please check that the compiler here was chosen correctly?

From your logs:

"ClCompilerPath" was not found.
"CLToolExe" was not found, falling back to cl.exe.
C:\Program Files\BullseyeCoverage\bin\cl.exe

Kennet · April 1, 2025, 6:50am

I have Bullseye install and is using it sometimes. The path is correct and the solution builds ok. I have now tried to uninstall Bullseye to see if that makes a difference.
This is the log output after I did that on a new solution:

Initializing the telemetry package...
Finished initializing the telemetry package...
Initializing the daemon package...
[Connection Migration] The connections.json file already exists. Migrating connections from existing bindings was not performed
Current VS version:
    Visual Studio Professional 2022
    17.13.35919.96
    17.13.5
[SLCoreHandler] Creating SLCore instance
[SLCoreHandler] Starting SLCore instance
Settings file does not exist at "C:\Users\kniels\AppData\Roaming\SonarLint for Visual Studio\settings.json".
Default settings will be used
[NodeJSLocator] Checking environment variable SONAR_NODEJS_PATH
[NodeJsLocator] Environment variable is not set
Finished initializing the daemon package.
[SLCore] Can't open directory channel. Log directory fsync won't be performed.
Solution/folder is not in a git repository
[SLCore > Workspace Files > Tracking] Configuration scope not initialized
[Connected Mode > Shared Binding] The shared binding configuration file was not found and will not be used. Probed path: not found
Updated analysis readiness: True
[SLCoreAnalyzer] Analyzing C:\Users\kniels\source\repos\Testing\ConsoleApplication5\ConsoleApplication5\ConsoleApplication5.cpp with id e100ca44-db43-4de9-9c1c-613fb9d7b65c
C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.43.34808\bin\HostX64\x64\cl.exe
Initializing the notifications package...
Not connected: not checking for notifications
Finished initializing the notifications package
[Connected Mode > Shared Binding] The shared binding configuration file was not found and will not be used. Probed path: not found
[SLCore] Node.js could not be automatically detected, has to be configured manually in the SonarLint preferences!
[SLCore] Failed to recover to valid root, address = 42907710, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42859235, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42810368, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42758403, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42702700, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42643539, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42581632, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42513832, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42498416, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42480532, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42464491, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42448450, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42432409, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42406807, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42386035, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42316704, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42296480, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42275797, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42206321, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42185484, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42162177, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42091800, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42064695, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42044448, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42022893, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42003099, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 41983305, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 41960620, file = 00000001800.xd
[SLCore] Unexpected error occurred in scheduled task
[SLCoreAnalyzer] Finished analyzing C:\Users\kniels\source\repos\Testing\ConsoleApplication5\ConsoleApplication5\ConsoleApplication5.cpp with id e100ca44-db43-4de9-9c1c-613fb9d7b65c, analysis time: 5,403s
[SLCoreAnalyzer] Analyzing C:\Users\kniels\source\repos\Testing\ConsoleApplication5\ConsoleApplication5\ConsoleApplication5.cpp with id 48e53808-94da-4cfc-9c7f-49be3931c607
C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.43.34808\bin\HostX64\x64\cl.exe
[SLCore] Failed to recover to valid root, address = 42907710, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42859235, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42810368, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42758403, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42702700, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42643539, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42581632, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42513832, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42498416, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42480532, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42464491, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42448450, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42432409, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42406807, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42386035, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42316704, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42296480, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42275797, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42206321, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42185484, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42162177, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42091800, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42064695, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42044448, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42022893, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 42003099, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 41983305, file = 00000001800.xd
[SLCore] Failed to recover to valid root, address = 41960620, file = 00000001800.xd
[SLCore] Unexpected error occurred in scheduled task
[SLCoreAnalyzer] Finished analyzing C:\Users\kniels\source\repos\Testing\ConsoleApplication5\ConsoleApplication5\ConsoleApplication5.cpp with id 48e53808-94da-4cfc-9c7f-49be3931c607, analysis time: 0,616s

georgii.borovinskikh · April 1, 2025, 7:34am

Seems like you were unlucky to get 2 different issues at the same time.

Judging by the new logs the compiler is now correctly selected:

C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\MSVC\14.43.34808\bin\HostX64\x64\cl.exe

BTW, you didn’t have to uninstall your other compiler. Sorry if I wasn’t clear, but you could set ClCompilerPath property in your project or, alternatively, as an environment variable pointing to the correct compiler’s full path (above).

The second issue is with the local issue storage being corrupted for some reason. To fix that, please delete the following 2 folders:

%localappdata%\SLVS_SLOOP\storageRoot and ~\.sonarlint\storage

Kennet · April 1, 2025, 9:46am

Thanks.
Removing %localappdata%\SLVS_SLOOP\storageRoot fixed the issue.
Maybe you should update the VS plugin to remove this folder when you uninstall.

georgii.borovinskikh · April 1, 2025, 1:08pm

Unfortunately, Visual Studio does not give us any way to know that the extension is being uninstalled. We also share some of these files with SonarQube extensions for other IDE, so it might not be safe for us to assume that these files are no longer needed.

system · April 8, 2025, 1:10pm

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Getting error in visual studio 2022 for connect sonar lint Visual Studio	4	210	December 5, 2024
SonarLint not functioning on VS Studio 2022 Enterprise Visual Studio	15	63960	December 2, 2024
Having Issue while connecting SonarQube using Sonarlint for VS Visual Studio	15	1402	December 7, 2022
SonarQube plugin for Visual Studio IDE does now show errors/warnings Visual Studio	1	30	April 17, 2025
Visual Studio .slconfig is not getting created or there is no option to create one Visual Studio	1	56	July 23, 2024

Issues no longer appear in IDE

Related topics