Forum Discussion
Ownership and Refresh
!Solution!
In our case the error message proofed to be misleading - it had nothing to do with either ownership or access rights. We in fact created conflicting connections by substituting one report with a newer version that had different connections.
The following approach solved the problem for us:
1. delete everything from the workspace
2. manually delete all connections and gateways under "Manage connections and gateways"
3. re-publish the pbi report to empty workspace
Hi MK_PBI_USER ,
what is your data source?
Are there any Live connections (Sematic Model ) Pulled in your original report from another workspace?
The source is "Azure Data Lake Storage Gen2" with a scheduled weekly update. I cannot update the data via the Workspace anymore, it does however work perfectly on the desktop app. I also cannot go back to the previous version, as I also get the same error message there. I even tried publishing the report in a different workspace and got the same result.
I guess you use a gateway to go to the source.
The conncetion to the blob storage is still valid in Service (=online)? And you are able to use this connection?
