Report subscriptions running on incorrect schedule after database move
We have found that if we move the database to a different server that reports that are scheduled to run every 2 weeks will run on the incorrect week (not all of them, just some of them). This can be corrected by editing the subscription, edit the schedule, then clicking apply, click apply. Can this please be fixed or can this action be done programatically? We are running on an AG so a "database move" may happen at failover.
PBIRS Report subscription fails inconsistently
We have a newly set up PBIRS with May 2020 installed over SSRS 2016 and report subscriptions aren't working consistently. We've only published one report while we test the server. The report on a shared schedule only works about 40% of the time. About 60% of the time it generates the error: Failed to load expression host assembly. Details: Could not load file or assembly 'Microsoft.ReportingServices.ProcessingObjectModel, Version=2020.5.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The located assembly's manif When it works everything is logged normally but when this error comes up, I can't find any logging anywhere. I can only see the error on the "ReportName">Manage>Subscriptions page of the reports portal which is why the end of the message is cut off. I don't understand why it only works sometimes or what to do about it. Thanks
Error when creating subscription on linked report
I'm not sure if this is the appropriate place to put this as it's not a PBI report problem per se, but we are running PBI Report Server so I thought I would start here. We are getting the dreaded, vague "Something went wrong. Please try again later." error when trying to create a subscription on the linked version of an SSRS report. This happens whenever I try to set the value of a parameter. The error does not occur on when running the report either normally or when creating a subscription on the "base" report, only when it is a linked report. I've managed to reproduce the error by creating a very simple report. The main thing is that the report must have a cascading parameter. The error occurs as soon as I set the value of the first parameter in the subscription. We have upgraded to the March 2018 PBIRS release, but the same problem was happening with the October 2017 release as well. Any thoughts or ideas would be most helpful as we have a lot of reports using the exact scenario above (linked, cascading parameters with subscriptions) that worked fine in SSRS 2008/R2 and are still running, but can no longer be edited or new subscriptions created since we upgraded.