"The SonarLintIntegrationPackage did not load correctly" - Error in Visual Studio 2022

susu · December 9, 2024, 9:34am

Operating system: Windows Server 2019
Visual Studio version: 17.10.9
SonarLint plugin version: SonarLint.VSIX-8.7.0.11108-2022
Programming language you’re coding in: C#
Is connected mode used: Yes
- Connected to SonarCloud or SonarQube (and which version): SonarQube Developer Edition 10.8 (Evaluation)

And a thorough description of the problem / question:

I want to test sonarlint with sonarqube developer edition(14 day evaluation):

The SonarQube is already installed and is running without any problems.

I can install the LonarLint extension in VS 2022 without any errors and i see the new menue-items. If I click on these items, I get the right mask to the right funktionaltiy (BUT the extension is not shown in the Extension overview !?!?)

It is possible to change in the connected mode and bind to a project. BUT if I reopen Visual Studio, I get errors and SonarLint has no functionality anymore. I’ve found these articles with the same error description to this issue and tried all the workarounds (Delete MEF Componente Cache…) but no success :

https://github.com/SonarSource/sonarlint-visualstudio/issues/3029
https://community.sonarsource.com/t/visual-studio-integration-package-failing-to-load/53518

Because SonatLint is not shown in the extension overview of VS. I can only delete it if I use visxinstaller.exe /uninstall

Any ideas? I have to test it before I can buy it…

Colin · December 10, 2024, 7:39am

What errors do you get? Feel free to paste them here.

susu · December 10, 2024, 8:40am

The same that you see here in this thread:

Colin · December 10, 2024, 9:51am

Well, then I suggest following the reccomendations from that thread.

This error normally indicates a problem with the local VS installation, rather than the SonarLint VSIX itself. However, if uninstalling and reinstalling doesn’t fix the issue, please post the relevant section of the ActivityLog.xml in case that provides any pointers to the underlying issue.

susu · December 12, 2024, 7:36am

I‘ve spent hours to try out all the workarounds that I found in your community and the internet. Repair and Reset VS. Clear MFE Cache, deactivate other extensions and much more. No success. The installation of other extensions (Clear MEF Component Cache - Visual Studio Marketplace) runs without problems and I can see it in the extension overview at once. And they work without any problems.
Because I’m new to Sonar, which Logs do you need?

VS 2022 - ActivityLog.xml
vsixinstaller.log
???

And what’s about this bug in your team backlog?

github.com/SonarSource/sonarlint-visualstudio

[Install] SonarLint package fails to load

opened 08:31AM - 16 May 22 UTC

duncanp-lseg

Type: Bug

### Description Visual Studio shows an error dialogue reporting a package loa…d failure in a SonarLint package. SonarLint features are not available. ### Repro The failure is intermittent, and related to the VSIX installation. If the VSIX installation works correctly then the everything is fine. If the VSIX installation does not work correctly, the installation will be broken and will never work. 1. Install VSIX 2. Open a solution in Visual Studio ### Expected behaviour No errors - SonarLint works as expected ### Actual behaviour Visual Studio shows an error dialogue reporting a package load failure in a SonarLint package. Most SonarLint features are broken. ### Workaround Try the following: A) uninstall and re-install the extension. Note: when uninstalling, check whether there is a package called `SLAF` in the extensions list. If there is, manually uninstall it _after_ uninstalling SonarLint. or B) reset the MEF cache (using an extension like [Clear MEF Component Cache](https://marketplace.visualstudio.com/items?itemName=MadsKristensen.ClearMEFComponentCache, or by locating and deleting the appropriate folder e.g. `%localappdata%\Microsoft\VisualStudio\17.0_ff7fed4c`) #### Activity log extract ``` 34 ERROR SetSite failed for package [SonarLintIntegrationPackage]Source: 'SonarLint.2022' Description: Object reference not set to an instance of an object. System.NullReferenceException: Object reference not set to an instance of an object. at SonarLint.VisualStudio.Integration.Vsix.SonarLintIntegrationPackage.<InitOnUIThreadAsync>d__5.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 System.Runtime.CompilerServices.TaskAwaiter.GetResult() at SonarLint.VisualStudio.Integration.Vsix.SonarLintIntegrationPackage.<InitializeAsync>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 Microsoft.VisualStudio.Shell.AsyncPackage.<>c__DisplayClass20_0.<<Microsoft-VisualStudio-Shell-Interop-IAsyncLoadablePackageInitialize-Initialize>b__1>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.<JoinAsync>d__76.MoveNext() {68D6A325-11E8-4790-A4BA-0EDD001FB080} 80004003 - E_POINTER VisualStudio 2022/05/16 07:15:13.668SetSite failed for package [SonarLintIntegrationPackage]Source: 'SonarLint.2022' Description: Object reference not set to an instance of an object. System.NullReferenceException: Object reference not set to an instance of an object. at SonarLint.VisualStudio.Integration.Vsix.SonarLintIntegrationPackage.<InitOnUIThreadAsync>d__5.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 System.Runtime.CompilerServices.TaskAwaiter.GetResult() at SonarLint.VisualStudio.Integration.Vsix.SonarLintIntegrationPackage.<InitializeAsync>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 Microsoft.VisualStudio.Shell.AsyncPackage.<>c__DisplayClass20_0.<<Microsoft-VisualStudio-Shell-Interop-IAsyncLoadablePackageInitialize-Initialize>b__1>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.<JoinAsync>d__76.MoveNext() ``` ### Notes The issue caused by MEF cache corruption. Normally MEF cache corruption won't cause visible failures - components won't be imported, so features won't be available. However, we programmatically fetch some MEF components during package load, and then call those components without checking whether they are null or not. The package initializers have `try-catch` blocks to prevent initialization errors from propagating to the UI, and the `catch` block attempts to log the failure to the Output Window. However, the logger component is also MEF-imported, so if the cache corruption prevents the logger from being imported then the `catch` blog will throw a null reference exception when calling `logger.WriteLine`. ### Possible solutions The underlying problem is MEF cache corruption, which we can't control or prevent. However, we could improve the UX by avoiding turning the MEF error into a package load failure, and by providing a better error message. ##### Initial proposal * check all packages have try-catch blocks in the initializer * add a extension method to fetch the logger. If the logger can'b be retrieved via MEF, the method instantiates one directly and logs a message saying there is a MEF error. * evaluate the UX. How often is the message logged? How noticeable is it? Could we show a gold bar instead? * add a wiki page describing the symptoms and how to work round them. #### Affected versions Visual Studio: all SonarLint: all

Colin · December 12, 2024, 9:44am

If you have both these logs available, please share them for review.

susu · December 16, 2024, 11:33am

Hi Colin,
I’ve made screenshots, a description of my installation process (PDF) and shared my logs. Hope you can help me…!
SonarLint.zip (244.0 KB)

vnaskos · December 16, 2024, 1:59pm

Hi Sven,

Thank you for sharing your Visual Studio logs. I’m sorry to hear about the challenges you’re facing.

After reviewing the logs and comparing them with the details in your ticket, the root cause remains unclear. However, I did notice that your journey began with SonarLint version 8.7, and it appears you later upgraded to version 8.8. With this update, SonarLint was rebranded as SonarQube for IDE (or in this case SonarQube for Visual Studio 2022). This transition might have introduced a conflict during installation.

To rule out this possibility, I’d recommend performing once again a Reset VS and then reinstalling the latest version of SonarQube for Visual Studio 2022 (8.8.0.11278). This will help us confirm whether the rebranding plays a role in the behavior you’re observing.

Please let me know if you encounter any further issues or if there’s anything else I can assist with.

Best regards,
Vasileios Naskos

susu · December 18, 2024, 7:56am

After hours of searching… The solution was to delete this file in Visual Studio:
C:\Users\XYZ\AppData\Local\Microsoft\VisualStudio\17.0_f877cd4f\privateregistry.bin
If Visual Studio is newly opened, it creates a new one. Then I could install the SonarLint - Extension and i can see it in the extension administration. No Error logs. Yeah!

system · December 25, 2024, 7:57am

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