The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
Hello,
since yesterday, one of our reports that was working fine before, can't open anymore on powerbi service. It goes in an endless loading screen and there don't pop up any error message. Even after hours on this screen.
- Only this report
- I've already tried to clean cache, reload the report and refresh the dataset
- I've already tried to use other browsers
- It seems like the same problem like here in august:
Reports on Premium Workspace Load Forever
Thanks,
Fabian
Solved! Go to Solution.
Hi,
thank you for your answer.
We are using Direct Queries as connection types. But when I opened other reports which base on the same power bi dataset there was no problem. So it should not be a problem with locked tabels.
Republishing was also not an option as the report was builted in power bi service.
But when I tested the involved reports again this morning, there was no longer a problem. I don't know if microsoft did an update or something like that, but I didn't make any further changes in the reports. In the Topic from august, which i linked above, a similar behavior occurred.
Hi @fm777 ,
What connection type you used ? See if there are problems with the source data. (e.g. if the tables in the database are locked)
Try to download pbix file and open it use Power BI desktop, check if it could be opened?
If this is OK, try republishing.
Did I answer your question? Mark my post as a solution!
Best Regards
Lucien
Hi,
thank you for your answer.
We are using Direct Queries as connection types. But when I opened other reports which base on the same power bi dataset there was no problem. So it should not be a problem with locked tabels.
Republishing was also not an option as the report was builted in power bi service.
But when I tested the involved reports again this morning, there was no longer a problem. I don't know if microsoft did an update or something like that, but I didn't make any further changes in the reports. In the Topic from august, which i linked above, a similar behavior occurred.