Forum Discussion
Couldn't load the model schema associated with this report. CannotRetrieveModelException
I am trying to make a report by automating the data loading using dataflow gen2 and storing them in lakehouse. Data is being fetched from azure blob container.
I am doing this in a premium workspace generated by my organization.
After running the dataflow when I try to create the report using the dataset generated by dataflow, I get the error below:
**(This happened earlier as well but somehow resolved itself and then I was able to make the flow as I needed, since yesterday I have been facing the same issue again and cant solve it)**
Cannot load model
Couldn't load the model schema associated with this report. Make sure you have a connection to the server, and try again.
- Underlying ErrorCapacity operation failed with error code CannotRetrieveModelException
- Activity ID94740d61-bad4-4018-ab95-fcb352795d7c
- Correlation ID24d2fc1a-7989-4ba9-5f2b-ed06ae5d74a6
- Request ID7c2afd9e-bd4e-7c50-c4d3-4514f53c29d7
- TimeFri Dec 27 2024 15:49:02 GMT+0530 (India Standard Time)
- Service version13.0.24766.32
- Client version2411.3.21980-train
- Cluster URIhttps://wabi-us-east2-d-primary-redirect.analysis.windows.net/
Hi abhishekJ
The error likely stems from one of these issues:
Dataflow or Dataset Issue: Ensure the dataflow ran successfully and the lakehouse data is intact. Manually refresh the dataset to verify.
Premium Capacity Overload: Check if your workspace capacity is near its limit. Optimize workloads or increase capacity if needed.
Connection Problem: Verify the Azure Blob connection in the dataflow and check the lakehouse schema for changes.
Service Interruption: Confirm if Power BI services in your region are operational via the Power BI Support Page.
Report Issue: Try republishing the report or recreating it with the dataset.
If unresolved, share the Activity ID and Correlation ID with Microsoft Support for further assistance.
Did I answer your question? Mark my post as a solution, this will help others!
If my response(s) assisted you in any way, don't forget to drop me a "Kudos" 🙂
Kind Regards,
Poojara
Data Analyst | MSBI Developer | Power BI Consultant
Consider Subscribing my YouTube for Beginners/Advance Concepts: https://youtube.com/@biconcepts?si=04iw9SYI2HN80HKSThe error was due to not having assigned a default semantic model. Thanks!
7 Replies
- Poojara_D12
Super User
Hi abhishekJ
The error likely stems from one of these issues:
Dataflow or Dataset Issue: Ensure the dataflow ran successfully and the lakehouse data is intact. Manually refresh the dataset to verify.
Premium Capacity Overload: Check if your workspace capacity is near its limit. Optimize workloads or increase capacity if needed.
Connection Problem: Verify the Azure Blob connection in the dataflow and check the lakehouse schema for changes.
Service Interruption: Confirm if Power BI services in your region are operational via the Power BI Support Page.
Report Issue: Try republishing the report or recreating it with the dataset.
If unresolved, share the Activity ID and Correlation ID with Microsoft Support for further assistance.
Did I answer your question? Mark my post as a solution, this will help others!
If my response(s) assisted you in any way, don't forget to drop me a "Kudos" 🙂
Kind Regards,
Poojara
Data Analyst | MSBI Developer | Power BI Consultant
Consider Subscribing my YouTube for Beginners/Advance Concepts: https://youtube.com/@biconcepts?si=04iw9SYI2HN80HKS Hi Poojara_D12 thanks for the reply,
1) Dataflow is working fine and data is being loaded in dataset perfectly.
2) I was able to create multiple reported and paginated reports as well earlier(when the issue resolved on it own earlier), does not seem to be a capacity issue if keeping that in mind.
3) Connection to azure blob container is correct working fine as I am able to load data in dataset when dataflow runs- Poojara_D12
HI abhishekJ
The issue might be caused by model schema corruption, dataset connectivity problems, caching issues, or large model complexity. Try refreshing the dataset, clearing the cache, or re-publishing the report. Ensure the connection to the data sources is stable, and check for any service disruptions. If the issue persists, test in a different workspace or contact Power BI support for further assistance.
Did I answer your question? Mark my post as a solution, this will help others!
If my response(s) assisted you in any way, don't forget to drop me a "Kudos" 🙂Kind Regards,
Poojara
Data Analyst | MSBI Developer | Power BI Consultant
Consider Subscribing my YouTube for Beginners/Advance Concepts: https://youtube.com/@biconcepts?si=04iw9SYI2HN80HKS
v-pnaroju-msftCommunity Support
Hi abhishekJ,
We are following up to see if your query has been resolved. Should you have identified a solution, we kindly request you to share it with the community to assist others facing similar issues.If the response was helpful, please mark it as the accepted solution and provide kudos, as this helps the broader community.
Best regards,
Pavan
The error was due to not having assigned a default semantic model. Thanks!
- v-pnaroju-msft
Hi abhishekJ,
We are pleased to hear that your issue has been resolved. Kindly mark the response that resolved your issue as the accepted solution. This will help other community members facing similar challenges to find solutions more efficiently.Please continue using Fabric Community for any help regarding your queries.
Best regards,
Pavan
- v-pnaroju-msft
Hi abhishekJ,
We are delighted to know that your issue has been resolved. Kindly mark the response that resolved your query as the accepted solution. This will assist other community members facing similar challenges in finding solutions more efficiently.
Please continue to utilise the Fabric Community for any further assistance with your queries.
Thank you.