Forum Discussion
PowerBI Reports based on Direct Lake Semantic Model are not loading
Hi ismail_ozturk,
1) When were these reports published and how long have they been in the power bi service.
2) Were there any changes done to your fabric workspaces where the lakehouse in the last 3 days proir to this issue occured and any changes related to OneLake security roles or configuration changes.
3) were there any updatres rolled out from microsoft side during this period.
4) who owns this semantic model and Report. did anything specific to this owner change in the Workspace.
Review OneLake security roles You may need to be added to an existing role or create a new one that grants proper access.
- ismail_ozturk7 months ago
Advocate I
Hello Santhanam,
I am writing my answers below. Thank your for help
1) These reports were published about a month ago.
2) No we didnt change anything including semantic models, lakehouses and reports.
3) I dont know this one. MS is changing something everyday you know.
4) The same user actually and there is no change about it.
The most interesting part is that after manuel refresh the report works but after a while it gives the same error.
Best regards
İsmail
- Santhanam7 months ago
Resolver I
Refreshing the semantic model manually can temporarily resolve the issue, but it may recur until the security configuration is stabilized.
Try creating a duplicate of the existing role and adding the owner and other users present in the original one into this new role. and check if this fixes the issue.
since you have already mentioned that you had reached out to Microsoft support and they were not able to find the root cause.
im sure microsoft has already taken a note of this issue and will try to fix this in the next 24 to 48 hours.- ismail_ozturk7 months ago
Advocate I
Hello Santhanam,
I hope Microsoft will. By the way I dont think it is related to onelake security because when we get error from reports, we can not see any tables in direct lake semantic model. Also I am the fabric admin and ws admin but I have also this error when loading report.
Best regards
İsmail