Forum Discussion
PBI Server May 2020 not refreshing saved reports
Anonymous wrote:
So, the only workaround is to return to Jan 2020 version?
Is it safety just to install the older version?So one workaround is open your report in desktop, then go back to the portal and delete the file from there before you save. But that is not great for end users.
Otherwise you either have to wait for a fix or look at going back to Jan 2020. Although Ideally you should restore the ReportServer database from a backup as I'm not sure if the May release made any schema changes or not.
Realistically my guess is that it could be at least a week or two, maybe longer before an update is published. Even if they have a fix for this today Microsoft will need to do a full test run to make sure that the fix does not break anything else. The last thing they want to do is rush out a fix that breaks something else.
Anonymous
Try running a simple 'Refresh All' on your local after any changes are made and just before you republish the Report back to the Report Server. I found that this workaround worked with the issue I was having which looks to be similar to yours, see: Bug: Power BI Report Server - Scheduled Refresh rolling back Report to previous version
As to why this works, I'm not actually sure - in addition to updating the Reports datasets the 'Refresh All' almost seems to run a build of sorts which prevents the changes to the new version being rolled back to the older vesion after a scheduled refresh is completed, I'm only guessing here though.
josef78Memorable Member
Anonymous it is totally different issue. In your case is not correctly updated layout definition, only sometimes, also on pre May 2020 version, and exist simple and reliable workaround.
This issue is related only to May 2020 PBIRS, and affecting all reports in all cases when refreshing data on PBIRS. The issue is simple, when model si loaded in to cache (integrated SSAS tabular instance) and data are refreshed (manually from PBID or scheduled on PBIRS), then data in cache are not retried and stay in cache, and PBIRS still use old data in cache. Old data in cache stay until model is removed from SSAS, and it can happen only when PBIRS (including integrated SSAS) is restarted, or model is not used for expiration time (by default more than hour).
Issues is simple, but full workaround is not possible. To reduce impact of this issue, can help decrease expiration time (in SSMS) and for low usage reports it help, but for business critical reports with heavy usage (is used constantly) this is not helpful, only solution is restart PBIRS to remove SSAS cache (or remove SSAS DB manually directly on SSAS instance). E.G. If you have critical reports which are refreshed every hour and this reports are constantly in use over day, data in reports stays on morning version, and only workaround is restart PBIRS every hour.
- josef78
additional workaround how reduce impact of this issue is decrease ModelCleanupCycleMinutes and ModelExpirationMinutes parameters in SSMS of RS. Which reduce time to retried model from cache, and load fresh model from DB. But it works only for reports which are not used constantly (expiration time is counting only when reports is not in use)
- josef78
Additional info: (probably, in my case) if PBIRS is running only on one server, this issue affecting only manual dat refresh from PBID.
If PBIRS is runnning on multiple servers and data refreshes are running on different sever than front end PBIRS (directed by IsDataModelRefreshService settings in rsreportserver.config) this issue affecting both, manual data refresh from PBID and also scheduled data refresh on PBIRS server.
Anonymousif you mean Refresh All in Query Editor, i have tried but no success.
No, try a 'Refresh All' on the Report view.
- josef78
Anonymous 'Refresh All' on the Report view does not help for this issue. It is not affecting out of date SSAS cache.
SSAS cache (on PBIRS instance) is not reloaded (if already loaded in cache) for used PBI report on PBIRS after data are updated in DB (on MSSQL instance), does no matter if data are updated from PBID or Scheduled refresh.