Gateway not configure correctly

[rredford]

Hi all

I have successfuly installed a gateway on a server and connected to it through Fabric Admin. I have also managed to create a connection for a data source and it shows as online.

In Gateways and Connections

• Gateway 'Online'
• Datasource 'Online'

But if I go to the report and semantic model and refresh and look at the Gateway and cloud connections I still get the below. Addmittedly I have only created a connection so far for the first and top data source in the list below. But surely it would not still have a red cross against it and request I 'add to the gateway' when I have already and it shows as 'online'?? What am I doing wrong. This source is a excel file in a shared folder on our file server.

Kind regards

Rob

[v-saisrao-msft]

Hi @rredford,
I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, please Accept it as a solution and give it a 'Kudos' so others can find it easily.
Thank you.

[v-saisrao-msft · Accepted solution]

Hi @rredford,

Thank you for reaching out to the Microsoft Fabric Forum Community. 

While your gateway and one data source are showing as online, Power BI (or Fabric) requires that every data source used in the semantic model be registered with the gateway and then explicitly mapped within the dataset settings. 

Even though you’ve configured a connection for the Excel file, the other two still need to be added to the gateway. The Excel source you’ve already configured, make sure the file path used in Power BI Desktop exactly matches the one in the gateway settings. If the dataset uses a mapped drive (like Z:\Reports\file.xlsx) and the gateway is set up with a path (\\ServerName\Reports\file.xlsx), Power BI will not consider them the same causing the red status to persist. 

Ensure all three sources are added to the gateway using paths (not mapped drives) and then go to the “Gateway and cloud connections” section of the dataset settings. There, use the “Add to gateway” option to manually map each source to its corresponding entry in the gateway. Once every source is correctly mapped and saved, the configuration status should update, and refreshes should proceed without issue.

If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.

Thank you.