Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes! Register now.
Hi,
We have recently upgraded the Power BI server from March 2018 to January 2019 version, the reports which are already exists with schedule refresh are continue to refresh properly after upgrade, however when we upload any new report and configure the schedule refresh. It is not initiating the refresh on the schedule timing. When we initiate manually by selecting the schedule and clicking the "Refresh now" button, the status is set as "Refreshing" but nothing happen thereafter. The status remains set with "Refreshing" and not changing further. The only way to revert the status is by deleting the schedule.
We checked the log file too, but not finding any related error messages.
We tried restarted the power bi services, set a valid execution account in report configuration manager but nothing helps.
We didn't find this issue reported anywhere before in the forum.
Can we get some solution for this problem?
Thanks
Solved! Go to Solution.
Resolution:
This issue was taken up with Microsoft support and they have resolved it.
I'm publish the resolution for the sake of other users who may face this issue can try out it.
The Event table in ReportServer database has piled up with entries for long and under normal situation there should no be any rows in event table.
The reporting service has a polling service which queries the Event table in every 10 seconds by default. Since there were thousands of records stayed in Event table the leads to reporting service failure. After cleaning those event records the schedule refresh starts working perfectly.
Thanks
Mani
Resolution:
This issue was taken up with Microsoft support and they have resolved it.
I'm publish the resolution for the sake of other users who may face this issue can try out it.
The Event table in ReportServer database has piled up with entries for long and under normal situation there should no be any rows in event table.
The reporting service has a polling service which queries the Event table in every 10 seconds by default. Since there were thousands of records stayed in Event table the leads to reporting service failure. After cleaning those event records the schedule refresh starts working perfectly.
Thanks
Mani
Thank you, Anonymous!
It was the only message in community about that problem.
And your solution helps!
God bless you )
User | Count |
---|---|
12 | |
3 | |
2 | |
2 | |
2 |