Forum Discussion

nigama's avatar
nigama
Advocate I
1 year ago
Solved

Power BI Report Publishing Error - Disconnected File


Details:
  • Data Sources Used: Direct Query from Dataverse tables and SQL Server.
  • Custom Tables: I have created a couple of custom tables for some visualizations within my Power BI Desktop before publishing.
1. Every time I publish my report to the Power BI Service from Power BI Desktop, I encounter a pop-up message stating, "Your file published but disconnected." It then advises me to connect by going to the semantic model settings or asking the semantic model owner for help.

 

2. When I click on "Open Dataset Settings," it redirects me to the Power BI Service and displays the following message:
Error Message: "One or more cloud data sources for this semantic model have been deleted."

 

 

3. Also, when I open my report in Power BI service I see this error message on top header:

 

4. When I click on show details, I see this pop up:
 
5. This is what I see under gateway and cloud connections and even when I select a personal gateway, I see an error
6. Error:

 

7. Also, the data source connections tab is greyed out
Need Help
  • MasonMA's avatar
    MasonMA
    1 year ago

    nigama 

     

    Hi, based on your pictures, in your Cloud connections you would first need to involve IT/Admin to have your data source mapped to either 'Personal Cloud Connection' or 'Shareable Cloud Connection' as semantic model needs to know how to connect to the data source.

    An example below. 

    Once done you may need to edit your Credentials again.

     

    Hope this helps:) 

4 Replies

  • MasonMA's avatar
    MasonMA
    Super User
    1 year ago

    nigama 

     

    Hi, based on your pictures, in your Cloud connections you would first need to involve IT/Admin to have your data source mapped to either 'Personal Cloud Connection' or 'Shareable Cloud Connection' as semantic model needs to know how to connect to the data source.

    An example below. 

    Once done you may need to edit your Credentials again.

     

    Hope this helps:) 

  • Royel's avatar
    Royel
    Super User
    1 year ago

    Hi nigama you are almost there, due to having more than 1 connection for a single source power bi get confused to select the connection by itself, or generally it happend when you publish a new report. 

     

    On your step 5 you need to select the actual connection marked area and then click Apply 

     

    If you don't see anything under map, then create a new connection and set it, and your problem will be solved. 


    Thanks, and let me know your progress? 

  • v-hashadapu's avatar
    v-hashadapu
    Community Support
    1 year ago

    Hi nigama , Thank you for reaching out to the Microsoft Community Forum.

     

    This happens because the SQL Server connection in your report uses DirectQuery and the Power BI Service needs a way to reach that on-prem source. Unlike Dataverse, which connects automatically in the cloud, SQL Server requires a standard data gateway and a matching data source registered in the Power BI Service. Right now, that connection doesn’t exist or isn’t mapped, which is why you're seeing the disconnected message, a grayed out credentials section and the error about cloud sources.

     

    Go to the Manage Gateways section in Power BI Service and register the SQL Server source using the same server and database name used in your report. Then, in the dataset’s Gateway and cloud connections settings, map the dataset to that source and apply. This will reconnect your semantic model and remove the error.

     

    Using an on-premises data gateway in Power Platform dataflows - Power Query | Microsoft Learn

    How to access on-premises data sources in Data Factory - Microsoft Fabric | Microsoft Learn

    Data source management - Microsoft Fabric | Microsoft Learn

    Install an on-premises data gateway | Microsoft Learn

  • nigama's avatar
    nigama
    Advocate I
    1 year ago

    I tried to publish a test report which uses only dataverse tables and it worked perfectly.
    Then I created another test report that uses data from SQL server and I get the same error: