I have set shared schedule for few dashabords which is getting expired after first execution. why so? attached Screenshot.
2 Comments
- v-qiuyu-msft
Community Support
Hi 9028194316,
Please go to SSMS, please execute the query below:
Use <your report server DB name> Go select c.Path, c.Name,rs.ScheduleID,s.StartDate,s.LastRunTime,s.LastRunStatus from Catalog c
join [dbo].[ReportSchedule] rs on c.ItemID=rs.ReportID
Join Schedule s on rs.ScheduleID=s.ScheduleIDYou will find the ScheduleID for the corresponding report, then go to SQL Server Agent -> Jobs, find the job based on ScheduleID, check the job history about this job.
Best Regards,
Qiuyun Yu - CopyAndDataNew Member
Hi,
We're getting a visualization bug regarding Shared Schedules on the Reporting Central web portal after upgrading to the PBIRS August 2018 version (15.0.2.540). After each schedule is executed, whether newly created or pre-existing before the upgrade, the [State] column is uncorrectly updated on the underlying ReportServer dbo.Schedules table, and the [NextRunDate] column is set to NULL (obviously, we have not defined an expiration date):
Therefore, schedule displayed as Expired on the web portal:
...But it keeps executing correctly as that the jobs on the SSREL instance mantain their correct schedule (see job name same as ScheduleID):
This issue does not affect functionality but it gets a bit annoying in terms of administering schedules from the Reporting Central portal, as one can't tell without browsing to the SSREL jobs whether a schedule is really expired or not.
Thanks,