Thanks for that, I made these changes yesterday and could open the Power BI reports but a colleague couldn't even after he refreshed his cache.
Not sure this is related but it appears when you publish new reports to the Report Server and go to manage the report in the URL, there isn't the option to: As the Viewer Viewing the report. Has the upgrade changed this capability?
Could this be why my colleague is not able to open the reports. We have the Report Server on a separate box to the SQL Server.
Does this upgrade take into account any mods made for kerberos settings in the config file?
This sounds like a differant issue and unrelated to the config file changes. By 'As the viewer viewing the report' I assume you're referring to the DataSource properties settings. What type of DataSource are you trying to edit PBIX or RDL? Also what type of DataSource are you connecting to?
All RDL reports are now rendering sucessfully after updating the config files and restarting the service. We were not using snapshots or caching. Also, not all of our RDL reports were affected by this issue.
When can we expect to see an updated installer? Thanks.
@Ccparkhill I missed the fact that the supplied XML was only the Assembly Binding....thats what you get for reading on a phone. Thank you for the clarification.
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?