Forum Discussion
Method not found: 'Void Newtonsoft.Json.JsonSerializerSettings..ctor(Newtonsoft.Json.JsonSerializer"
One of those dependencies is a culprit. I just set up a brand new environment with Mar 26 release of PowerBI AND WITHOUT any of the external tools in the screenshot and was able to open the same PBIP without any issues.
Advocate IIn our environment it is looking like that "problem" dll in the GAC is a Dell signed version, so likely installed as part of our SOE build. The older version, 13.0.1.25517 was an issue for us, but later builds with 13.0.4.30916 are fine.
We have found the same thing. Dell Command Monitor is installing it for us. It may also be installed wiht other Dell products but that one for sure did it on a clean install here. We have been working with Microsoft and they are telling us to just delete the Dell installed dll from the GAC however that goes against everything I can find in Microsoft provided documentation. We still have an open ticket but this is definitely a regression in Power BI and instead of fixing the binding in the application they are relying in us to fix it by potentially breaking other software that we use fleet wide.
RuiRomanoMSMicrosoft Employee
Unfortunatelly we cannot fix the binding because all 13.x versions of this library share the same assembly version (13.0.0.0), Power BI Desktop as any other .Net application will prioritize the version in GAC.
Does the documentation here not show how to force binding to a specifc dll? If .NET Framework truly can't over ride the binding to a strongly-named assembly int the GAC then that seems like a huge oversight in the framework itself.
Specifying an Assembly's Location - .NET Framework | Microsoft Learn
