Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
6 years ago
Solved

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 ope...
Report Server
  • d_gosbell's avatar
    d_gosbell
    6 years ago
    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.

d_gosbell's avatar
d_gosbell
Super User
6 years ago
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's avatar
josef78
Memorable Member
6 years ago

d_gosbell sorry, previous comment is for you

  • bradsy's avatar
    bradsy
    Microsoft Employee
    6 years ago

    Hi josef78,

     

    We have a fix underway, it is in the testing and validation phase. The current plan is to get it working, tested, then to release an update. It will be done as soon as we can. When I hear more about a date, I will post again.

  • bradsy's avatar
    bradsy
    Microsoft Employee
    6 years ago

    Yes, we are looking at it. No ETA, as we don't know how to fix yet.

  • josef78's avatar
    josef78
    Memorable Member
    6 years ago

    bradsy d_gosbell  Great thanks, I will wait for any new information about ETA and any solution about this issue.

     

    It's very important for me, because I have this version on production environment in large scaled-out deployment with many thousand users with continuous usage of business critical reports. Go back to Jan20 is very complicated, and workarounds for this issue is very limited (only restart PBIRS service every hour). I work on some additional workaround (checking SaveToCatalog action, connecting to SSAS instances, and deleting related DB from SSAS to force reload it), but it is also complicated and terrible.

  • Anonymous's avatar
    Anonymous
    Not applicable
    6 years ago

    bradsy   Any news ?

  • bradsy's avatar
    bradsy
    Microsoft Employee
    6 years ago

    It is being worked on. This is a touchy area of the code and will take time to validate no more regressions. No ETA.

  • Anonymous's avatar
    Anonymous
    Not applicable
    6 years ago

    Hi bradsy  any news?

  • josef78's avatar
    josef78
    Memorable Member
    6 years ago

    bradsy same question, any new information or ETA?

  • josef78's avatar
    josef78
    Memorable Member
    6 years ago

    Great 🙂

    • Version: 1.8.7485.35104 (Build 15.0.1103.234), Released: June 30, 2020
      • Bug fixes
        • Fixed an issue in scale-out scenarios where reports weren't reflecting edits immediately in the server after upload

    I go to apply update to test farm, I hope that is finally solved

     

    Thanks 

     

  • d_gosbell's avatar
    d_gosbell
    Super User
    6 years ago

    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

  • messerjc's avatar
    messerjc
    Advocate IV
    6 years ago

    Thank you for the update either way. 🙂  Our newly integrated team is experiecing minor issues around this on our two prod servers so we'll be keeping an eye out for updates.

  • MattTurnerN's avatar
    MattTurnerN
    Frequent Visitor
    6 years ago

    bradsy Thanks for the update. We're holding off testing/upgrading to the May release because of this bug.

  • mpsrshl's avatar
    mpsrshl
    Advocate II
    6 years ago

    There is a new version released on 30-06-2020

  • bradsy's avatar
    bradsy
    Microsoft Employee
    6 years ago

    Great to see it shipped. Any thumbs up or down for anyone who has tried it?

  • TOK's avatar
    TOK
    Helper II
    6 years ago

    bradsy Updated yesterday, Thumbs up from me so far 🙂

  • MattTurnerN's avatar
    MattTurnerN
    Frequent Visitor
    6 years ago

    josef78 Ah, thanks Josef. Where did you find that changelog? Could you provide a link?

    Thanks

  • messerjc's avatar
    messerjc
    Advocate IV
    6 years ago

    Do we know if that's the only bug fix? Because that doesn't sound like it addresses the original issue of reports not refreshing...or am I misunderstanding the cause of the original problem? Maybe the issues we're seeing with some scheduled refreshes failing is some other problem...