Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
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?
Solved! Go to Solution.
@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.
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?
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.
Hi @messerjc sorry for delay (I have another issue with my community account). But yes, finally after this update I there no problem, it work well.
hey, I went ahead with it last Friday. No problems at all.
Hi @bradsy Thank you for the update.
We have an end date or a deadline to the adjustment?
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.
@Anonymous i had the same issue but after updating to 15.0.1103.232 the issue is gone. Just to say again: I refresh my reports manuallly, automatic refresh is not working.
@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.
@Anonymousif you mean Refresh All in Query Editor, i have tried but no success.
No, try a 'Refresh All' on the Report view.
@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.
@josef78 thanks for confirming issue, this does seem to be a separate issue altogether.
I just thought on the off chance that the workaround solution we found may have applied to your situation, unfortunately it has not.
I've just heard that a hotfix for this issue has been released. I've done some testing in my environment and as far as I can see this issue appears to have been fixed. The new version is 15.0.1103.232 and they've just updated the may 2020 download at https://aka.ms/pbireportserver so if you re-download from there and re-install it should update your server. (you can check which version you are currently running by going to the http://<yourserver>/reportserver endpoint)
Bad news! :(((((
This version (15.0.1103.232) not solving this issue completelly. This version solving refresh cache only in case of manual upload from PBID.
In case of scheduled refresh (in case when data refresh is processed on another server than frontend server in scale-out deployment) is still not solved. After data datarefresh data in SSAS cache are not retried on all servers and using cached out-of-date data.
This issue, after two weeks is still not resolved.
@josef78 wrote:
Bad news! :(((((
This version (15.0.1103.232) not solving this issue completelly. This version solving refresh cache only in case of manual upload from PBID.
In case of scheduled refresh (in case when data refresh is processed on another server than frontend server in scale-out deployment) is still not solved. After data datarefresh data in SSAS cache are not retried on all servers and using cached out-of-date data.
This issue, after two weeks is still not resolved.
@josef78 - can you describe your scenario in more detail - Do you have different servers set as "back-end" vs "front-end"? Can you provide step-by-step details for reproducing this issue? Do you have a support ticket number for this issue?
I tested a number of refresh scenarios and they all worked fine. But this was only on a single server instance, not on scale out configurations
@josef78 - no worries. I saw your previous reply anyway and I've passed on the repro steps to my contacts at Microsoft. I'm assuming that bradsy will have logged this issue anyway
Yes, we are looking at it. No ETA, as we don't know how to fix yet.
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
3 | |
2 | |
1 | |
1 | |
1 |