Forum Discussion
"File Published but Disconnected” Error When Publishing Power BI Report
Hello, I've did exactly what you've mentioned in your post (I've wrote about it as well in my previous posts) and it did not help.
I'm not using on-prem, datasources were mapped and problem occured both on personal connector and other created specific for this issue.
I was able to resolve the issue the problem is how.
There was a Data Activator created on top of the report/app I was using. Removing Data Activator completely, get rid of this issue. Do you know why?
in my opinion it's an error. Most of the things related to the power bi is sometimes barely working (including this forum, it's my second reply that somehow dissapears). It's not small report that throws an error. It's a huge app developed by couple of people that worked flawlessly for the last couple of months and suddenly it's this thing while none new datasource has been added.
As far as I remember what I'm using is Dataflow Gen1. and I don't quite understand what I should do. I don't have credentials and privilages to change anything on the backend side. Gen2 is this thing with Lakehouse?
This is how datasources looks on my end. I do believe that PowerBi.Dataflow is depreciated, connector states "legacy" as well.
Go to the settings page of the semantic model and look at the Data Source Credentials section. Maybe the Sharepoint access token has expired and needs to be renewed. For good measure, reapply all credentials for all four connections (OAuth2).
same thing. Had done it previously and did it again just few minutes ago and still the same message
Hi mati_gouda,
Thanks for reaching out to the Microsoft fabric community forum.
Try These -Upgrade connectors
Switch from legacy Gen1 dataflows to Gen2 or standard cloud connectors.
Ensure you’re not blocked by permissions when doing this.
Configure/update a gateway
If your model includes on-premises or mixed-source connections, you need a standard on-premises data gateway (personal gateway won't suffice for composite/direct query models).
After publishing, go to the dataset’s workspace - Settings- Gateway connection, and map each data source to the gateway
Validate Data Source Credentials
In the service, under Data source credentials, re-enter and confirm all OAuth2 credentials (SharePoint, dataflows, etc.)
Re-publish the PBIX
After making these changes, republish. The "disconnected" banner should disappear, and the dataset will resume scheduled and on-demand refresh.
If the response has addressed your query, please Accept it as a solution and give a 'Kudos' so other members can easily find it
Best Regards,
Sreeteja.
Community Support TeamHello,
upgrade connectors - As you see I'm already using proper Dataflow connectors. Which are Gen2 connectors? Are there any different connectors that I'm already using?
Configure/update a gateway - it's already done. Same thing.
Validate Data Source Credentials - validated, still same issue
Re-publish the PBIX - does not help. The report is refreshing but does not want to refresh when publishing.
