Forum Discussion
Issues with Report Refresh – Semantic Model Stuck
Dear Fabric Community,
I am using a Pro license of Power BI and facing an issue where two of my reports are not refreshing. They continue to attempt refreshing the semantic model without success. No error messages are displayed. Interestingly, the reports refresh successfully in Power BI Desktop, but the issue occurs only on the Power BI Service. For the past five days, I have been manually refreshing the reports in Desktop and publishing them to the service daily, but the problem persists.
I have already tried the following steps:
- Deleted the semantic model and republished it.
- Created a new workspace and published the reports there.
- Changed the PBIX file names and republished in both the old and new workspaces.
Despite these attempts, the issue continues. I would greatly appreciate any guidance or suggestions on how to resolve this problem.
Best regards,
Ali Abbas Rajput
My all Connections are also live ... there are no issue in there.
Red highlighted report's semantic models are stuck:
Hi Sir,
Thank you very much for your kind support and continuous follow-up regarding this matter.
Unfortunately, the issue is still persisting. At the moment, our IT department and Oracle Server Administration team are occupied with ongoing server maintenance and system upgrade activities. They are expected to be available by coming Monday, after which they will review and investigate the matter further with me.
I will keep you updated on Monday regarding the status and whether the issue has been resolved.
Thank you once again for your patience, cooperation, and valuable support. I truly appreciate your assistance throughout this process.
Hi 123abc ,
We really appreciate your efforts and for letting us know the update on the issue.
Please continue using fabric community forum for your further assistance.
Regards Hi v-nmadadi-msft ,
Thank you very much. I am pleased to inform you that the issue has finally been resolved.
After further investigation, I found that the ERP production table was not refreshing properly. The refresh process was taking approximately 6 to 7 hours and eventually stopping without completing successfully.
Our Data Administrator created a separate production table specifically for BI purposes. After connecting to the new table, the issue was successfully resolved.
I would like to sincerely thank the entire Factic Team for your outstanding support, continuous follow-up, and cooperation throughout this process. Your assistance is highly appreciated.
My Semenic model pic... Just for Info.
Hi 123abc ,
Glad to know your issue has been finally resolved, For any other Fabric or Power BI related issues Please continue using fabric community forum for your further assistance.
Regards
17 Replies
First of all Thank You So mcuh for your quick and prompt response. Thank You Agiain:
Following Error is now showing:
Refresh History is as below:
The detail is as per below:
Further detail is as per below:
Hi 123abc
With the error that you are showing, it could well be that the data source that you are trying to query could have an issue. What I would recommend doing is going on to your Power BI gateway and making sure that you can connect from the gateway to your data source as well as the gateway can connect to the Power BI service.
123abc Have you checked with the Oracle DBA if that query runs on teh database and why it doesn't finish?
No, Let my check.... but report is properly refreshed on desktop in 2 min 30 sec but not on BI service...🥺
Hi 123abc ,
It is possible that the refresh is failing due to a scheduled refresh timeout in the Power BI Service, particularly if the dataset refresh is taking longer than the allowed processing window or encountering resource constraints during execution.
Please try:
Reducing the model complexity. Simplifying the model, especially if it involves computationally expensive calculated tables and columns, can help to lower the refresh burden and avoid memory bottlenecks during refresh. If possible, move calculated tables and columns to the data source or ETL processes.Use incremental refresh for large semantic models. By automatically partitioning large tables, incremental refresh can help to reduce the amount of data that needs to be refreshed. By refreshing only the most recent import partitions, you can significantly reduce the refresh duration, thus making room for more refreshes in a given timespan.
Hi 123abc ,
Could you please confirm if the issue has been resolved after raising a support case? If a solution has been found, it would be greatly appreciated if you could share your insights with the community. This would be helpful for other members who may encounter similar issues.
Thank you for your understanding and assistance.
Hi Sir,
Thank you very much for your kind support and continuous follow-up regarding this matter.
Unfortunately, the issue is still persisting. At the moment, our IT department and Oracle Server Administration team are occupied with ongoing server maintenance and system upgrade activities. They are expected to be available by coming Monday, after which they will review and investigate the matter further with me.
I will keep you updated on Monday regarding the status and whether the issue has been resolved.
Thank you once again for your patience, cooperation, and valuable support. I truly appreciate your assistance throughout this process.
Hi 123abc ,
We really appreciate your efforts and for letting us know the update on the issue.
Please continue using fabric community forum for your further assistance.
Regards
