Forum Discussion
Helper IIAugust release - Failed to load expression host assembly
Microsoft EmployeeFor those affected can you validate in this files
"C:\Program Files\Microsoft Power BI Report Server\PBIRS\ReportServer\web.config"
"C:\Program Files\Microsoft Power BI Report Server\PBIRS\ReportServer\bin\ReportingServicesService.exe.config"
There is a configuration for Microsoft.ReportingServices.ProcessingObjectModel , it should look like the one below
focus in the values for oldVersion and newVersion
<dependentAssembly>
<assemblyIdentity name="Microsoft.ReportingServices.ProcessingObjectModel" publicKeyToken="89845dcd8080cc91" culture="neutral" />
<bindingRedirect oldVersion="9.0.242.0-2018.0.0.0" newVersion="2018.8.0.0" />
</dependentAssembly>
Feel free to change them and verify if that fix your issue, also if they are different that the one I showed, please post here the values you have.
Thanks
Partial fix only ---
We had the same issue after running the August PBIRS upgrade. After modifying both config files following the directions outlined by jtarquino, the report builder based reports successfully loaded ( so far, for the ones we tested)
With the input from others, problem below was from the Chrome cache, that needs to be cleared out.....
But, the Power BI Desktop reports are NOT now WORKING. They just hang, with the 'loading data' spinning round and round.
Tried uploading the PBI Desktop reports from PBI desktop, but that did not do anything.
Now what? did changing the ProcessingObjectModel break the newer PBI desktop reports, while allowing the older Report Builder reports to work?
adrez86Helper I
Have you tried deleting the cache on the browser you're using? That worked for me on the loading hangup for BI reports
pdbenbowResolver II
PBIuser01, what browser are you using? If Chrome, I suggest you run the reports in incognito mode and see if the problem still occurs. If the reports run OK in incognito mode, then return to regular Chrome and purge your browser cache, then try again.
I experienced the same issue you're describing after completing the upgrade, as did some of our business users, but only in Chrome. Using incognito mode will give you a hint as to whether it's a problem with your browser, and purging the cache should remedy the issue.