Forum Discussion
Desktop error after Live connection dataset refresh (cannot load model)
I am working with a live connection to a standard Power BI Dataset (shared).
I find I am receiving the following error frequently.
It appears to be correlated with dataset refreshes on the service.
For example, working fine at 7:55pm. Fails at 8:15pm, which is just after completion of a scheduled refresh.
I have not found a way to recover other than closing and reopening the PBIX file.
tommy_g You could check the Issues forum here:
https://community.powerbi.com/t5/Issues/idb-p/Issues
And if it is not there, then you could post it.
If you have Pro account you could try to open a support ticket. If you have a Pro account it is free. Go to https://support.powerbi.com. Scroll down and click "CREATE SUPPORT TICKET".Thanks. I did not know about the "Issues" forum, but this seems to be an "issue".
I will re-post there.
I'm still not sure how to classify this problem. The operative theory is that a refresh on the server breaks my current "live" connection. Hence the "delete, renamed, moved" comment. I can only assume a refresh recreates the dataset as a separate entity and when completely loaded, the "transaction" is committed and the original connection is broken. (still thinking like a SQL Server dev)
It does not appear to be an authentication issue in Desktop.
2 Replies
tommy_g You could check the Issues forum here:
https://community.powerbi.com/t5/Issues/idb-p/Issues
And if it is not there, then you could post it.
If you have Pro account you could try to open a support ticket. If you have a Pro account it is free. Go to https://support.powerbi.com. Scroll down and click "CREATE SUPPORT TICKET".Thanks. I did not know about the "Issues" forum, but this seems to be an "issue".
I will re-post there.
I'm still not sure how to classify this problem. The operative theory is that a refresh on the server breaks my current "live" connection. Hence the "delete, renamed, moved" comment. I can only assume a refresh recreates the dataset as a separate entity and when completely loaded, the "transaction" is committed and the original connection is broken. (still thinking like a SQL Server dev)
It does not appear to be an authentication issue in Desktop.