Forum Discussion
PBI Server May 2020 not refreshing saved reports
Last week I've updated Report server to version May 2020 (15.0.1103.227). I also updated Power BI Desktop (Optimized for Power BI Report Server - May 2020).
I notices the following issue: When I open the report with Edit in Power Bi Desktop, manually refresh data and change something small in report view, then save on PowerBI Report Server and refresh browser, nothing happens. In column Modified Date I see that the report has been modified, but in the report the data is old, like I never refreshed it.
After I restart the PowerBI Server (Stop then Start) the reports are refreshed.
I looks like there is a problem with the cache or something like that. Is there any new option in Power BI Desktop (Optimized for Power BI Report Server - May 2020) regarding this issue?
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.
56 Replies
Here we have the same situation.
We use Power BI in large scale, and we have many strategic reports and dashboards, that is used daily and after the upgrade to May 2020, the problemas with Cache started.
Our enviroment is composed by two servers in cluster:
Firts node is to render the reports and the second node only to schedule and refresh datasets.I tried to update the last version 15.0.1103.232 released on 6/15/2020 but don't work.
I tested too in a new servers, simulating my prod enviroment and the same problem.I hope Microsoft help us and relase a new version to fix this issue.
I have the same situation. Even, If you select "Edit in Power BI Desktop" you can see refreshed data. But on the Report Server old version report is displayed
I'm seeing a similar issue, I can make a small change like a background colour, then save to teh server and the background colour is updated but the data is still showing an earlier version.
I am also getting a sign in dialog almost every time I click on anything in the desktop client. It was never necessary to be signed in to the service in previous versions.
This definitely looks like a bug. There was a similar issue in the Jan 2020 release where schedule refresh would sometimes load an old copy of the model under certain circumstances. I've raised this with some contacts at Microsoft to see if I can find out what's going on.
The issue with multiple signin prompts seems to be triggered by third party visuals. So at the moment the work arounds for that are that you can either roll back to the Jan 2020 desktop version, not use custom visuals, or sign-in.
I also noticed that RLS stopped working. Does anyone have a similar problem?
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.
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.
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)
Hi bradsy Thank you for the update.
We have an end date or a deadline to the adjustment?
Great, latest version on my test enviroment works fine. On production I need some time to check, but I hope that it's solved 🙂
Hi Josef78, I'm assuming this has worked out well for you? Anyone else run into any problems with subscription refreshes since the update? I'm not seeing much other chatter about the problem so I'm going to go ahead with our updates and see how things go.
hey, I went ahead with it last Friday. No problems at all.
The June Hotfix solved the issue, to update existing Power BI Reports.
However we can't update existing Excel files anylonger. Very frustrating.
Does anybody have an idea?
