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.
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.
Super UserI'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)
josef78Memorable Member
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.
- d_gosbell
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
Anonymous repro steps I posted here https://community.powerbi.com/t5/Report-Server/Power-Bi-Reports-Refresh-Problem-with-May-2020-Updated-Version/m-p/1161348
This issue (after update to vertion 15.0.1103.232) is affecting only scale-out deployments with multiple servers, which some servers are dedicated only to web front end, and some servers are dedicated only to background data refreshes ( configured via <IsDataModelRefreshService> settings in rsreportserver.config)
Every PBIRS app istance have own SSAS instance (like cache) data are primary stored in MSSQL DB on another server. When user is accesing to report, server first check if data are in SSAS cache, if not will loaded (log action ASModelStream), and continue with loading schema and queries (ConceptualSchema and QueryData). Data in SSAS cache stay until report is not used for expiration period (by default one hour), or removed soon by memory cleanup process in memory pressure, or forced removed due to data refresch (not working in May 2020 version), and of cource when restart server.
When run scheduled data refresh, server load data from DB (ASModelStream), run refresh (DataRefresh) and store in DB (SaveToCatalog).
When rerun report after refrech on single instance deployment, the problem is not visble, because front-end and backgroud process are on single server and have shared SSAS cache, reported data are fresch because using same SSAS cache which has refreshed.
But if you rerun report in scale-out deployment, in May 2020 release, there missing step that retrie SSAS cache with old data on all PBIRS servers. When rerun report in scale-out deployment after data refresch, all severs must reload fresh data from DB.
This is big problem in lagre PBIRS deployment for critical business reporting. If you have single server, there is not problem now, because there is only one SSAS cache. If you have scaleout deployment, but you reports are refreshehed or used not often, there also not problem (if you are refreshing daily in night, and users open report morning, cache will be retried after some time). But if you are reports used for critial business process, and this reports are used constantly, SSAS cache never will be expired, and datarefresh NEVER affected (until restart all PBIRS front end servers)