Forum Discussion
Multiple reports connected to same dataset: Cannot load model error
Hi murfih ,
If I understand your scenario correctly that when you get data from power bi service with Power BI Dataset connector in power bi desktop, it will show errors and crash?
If so,I cannot reproduce your issue by my test, please check if you have installed the latest version of power bi desktop firstly.
In addition, do you have this issue for other dataset in power bi service or only this one?
Best Regards,
Cherry
Hi,
Yes you're correct with your understanding.
Currently we've only experienced the issue with this dataset, but we're only using this dataset connected to multiple reports. We tried to replicate it with another dataset, but without knowing what was causing it we could not.
We have altered how we distribute our reports by removing everyone from the workspace and having them access the reports via the app. Since then the issue hasn't reoccured, but we have been using the desktop files much less since, so it may be coincidence.
- Anonymous7 years agoNot applicable
I'm getting this issue as well. Just started happening with a data model I've had for a while. Fortunately its my "development" model. In this case i've separated my data model file and my report file. These reports are sitting in an old type workspace, which might be relevant.
Power BI doesn't actually crash, it just spawns 15 to 20 error messages, with more messages if you let it sit.
Getting through those messages, i can attempt to reselect the data model and when I do, i get the next 15 to 20 "We couldn't connect to your model in the Power BI Service. The dataset may have been deleted, renamed, moved, or its possible that you don't have permission to access it.
No OLE DB Error Information Found."I have a 2nd model in that same workspace, which is the production version. If I change the data source to point to that one, everything works. If i point it then back to the dev model, it fails again.
I've next tried deleting the model and publishing that model again. This has caused the report to connect and work again. I'll report back if this breaks again in the future.