Forum Discussion
Issue launching Report Builder after download
It is possible that you have NLog registered the Global Assembly Cache on your machine. If so, then that file will take precedence over the one that is meant to be used with PBIRB. I would suggest remove that file from the GAC, updating the file in the GAC or add a binding redirect to the exact version that PBIRB is using.
https://github.com/NLog/NLog/issues/4208
You can google how to do those options. The binding redirect would go into the PowerBIReportBuilder.exe.config file looks something like this:
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="Azure.Core" publicKeyToken="92742159e12e44c8" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-1.38.0.0" newVersion="1.38.0.0" />
</dependentAssembly>
Microsoft EmployeeIt is possible that you have NLog registered the Global Assembly Cache on your machine. If so, then that file will take precedence over the one that is meant to be used with PBIRB. I would suggest remove that file from the GAC, updating the file in the GAC or add a binding redirect to the exact version that PBIRB is using.
https://github.com/NLog/NLog/issues/4208
You can google how to do those options. The binding redirect would go into the PowerBIReportBuilder.exe.config file looks something like this:
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="Azure.Core" publicKeyToken="92742159e12e44c8" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-1.38.0.0" newVersion="1.38.0.0" />
</dependentAssembly>
Thanks, this led me to the solution! An application I was testing installed an NLog file on the Global Assembly Cache and this was interfering with Report Builder. Used the install date on the NLog file to determine what application it was. Uninstalled application and report builder opens fine now.
