Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
I'm not sure if I've uncovered a bug or what with a Power BI Data model that I built for our Sales/Finance team. The issue that I'm encountering is that the Power BI Service is unable to refresh the dataset, even though I have the Gateway configured, and the service works for other datasets. The only thing that I can tell that is different about this dataset from the others is that I am merging a query from a SQL table/view and Sharepoint hosted excel file into a table/query.
Basically, after spending hours trying to figure out what was unique, I've narrowed down the issue to the following situation:
Table RepDeptLookup.... is an excel file hosted on a sharepoint site that our Sales manager edits to put in department attributes for his sales team. The query is defined below (I've stripped identifying stuff from it):
let Source = SharePoint.Files("https://XXXXXXXX.sharepoint.com/Finance/", [ApiVersion = 15]), #"PowerBI_RepDeptLookup xlsx_https://XXXXXXXX sharepoint com/Finance/Shared Documents/" = Source{[Name="PowerBI_RepDeptLookup.xlsx",#"Folder Path"="https://XXXXXXXX.sharepoint.com/Finance/Shared Documents/"]}[Content], #"Imported Excel" = Excel.Workbook(#"PowerBI_RepDeptLookup xlsx_https://XXXXXXXX sharepoint com/Finance/Shared Documents/"), RepDept_Table = #"Imported Excel"{[Item="RepDept",Kind="Table"]}[Data] in RepDept_Table
Then there is table PBI_Users, which comes from a SQL view I created, that has a list of our Users. I merge this list with the sharepoint table above (RepDeptLookup) so that I can get the departments and notes that our manager has for his sales team added to the PBI_User table (which is highlighted in Red below):
let Source = Sql.Database("SQLServer", "CRM_DB"), dbo_PBI_Users = Source{[Schema="dbo",Item="PBI_Users"]}[Data], #"Filtered Rows (remove null employment status)" = Table.SelectRows(dbo_PBI_Users, each ([Employment Status] <> null)), #"Merged Queries" = Table.NestedJoin(#"Filtered Rows (remove null employment status)",{"SystemUserID"},RepDeptLookup,{"CRMGUID"},"RepDeptLookup",JoinKind.LeftOuter), #"Expanded RepDeptLookup" = Table.ExpandTableColumn(#"Merged Queries", "RepDeptLookup", {"Dept", "Notes"}, {"Lookup_Dept", "Lookup_Notes"})in #"Expanded RepDeptLookup"
Unfortunately, when I try to publish the dataset to the Power BI Service and configure it to automatically refresh, I get the following error:
We reached the data gateway, but the gateway can't access the on-premises data source.
But... If I remove the highlighted "red" lines from the PBI_User query and republish, I am able to successfully refresh the dataset via the power bi service.
And in both dataset scenarios, regardless if I use a merged query or not, I am able to refresh from the Power BI Desktop without issues.
SO MY QUESTION IS, how do I fix this issue? I want to be able to combine/merge my queries together regardless of the source, and I thought that's what Power BI allowed, but based on my testing, I can not do this. Also, can these error messages be any less helpful? I spent my whole day trying to figure out what was unique about this dataset to cause this issue, and I think I've done a good job given the very limited feedback that power bi error messages give.
Any help or suggestion or workaround would be greatly appreciated!
Solved! Go to Solution.
Hi @Namkce
Could I ask if you have set the Privacy settings on your Power BI desktop file to Always Ignore Privacy Level Settings?
As well as where you have configured your Power BI Gateway, is it installed as an Enterprise Gateway?
And following on from that have you also installed it with the latest version of the On-Premise Data Gateway?
And finally if you have got the latest version of the On-Premise Data Gateway installed, have you configured it to "Allow users clould data sources to refresh through this Gateway?
Hi @Namkce
Could I ask if you have set the Privacy settings on your Power BI desktop file to Always Ignore Privacy Level Settings?
As well as where you have configured your Power BI Gateway, is it installed as an Enterprise Gateway?
And following on from that have you also installed it with the latest version of the On-Premise Data Gateway?
And finally if you have got the latest version of the On-Premise Data Gateway installed, have you configured it to "Allow users clould data sources to refresh through this Gateway?
Thank you for your response and suggestions @GilbertQ
Your suggestion to update the Power BI Gateway seems to solve the problem. Below are my notes:
First, I took a look at the privacy settings and changed them from "Combine data according to each file's Privacy Level settings" to "Always ignore Privacy Level settings", and then saved/published my dataset to the Power BI Service and attempted a refresh, but still got the "'We reached the data gateway, but the gateway can't access the on-premise data source." error. (This was before updating the gateway.)
So then, I checked the Gateway. It's installed on one of the SQL servers that I'm accessing, and has access to the other SQL servers. The setting "Allow user's cloud data sources to refresh through this gateway cluster." was (and still is) enabled/checked in the Power BI Service.
However, one of the things that the Power BI Service complains about is our "On-premise data gateway version is older than August 2017", but I know I updated it in March 2018, yet I still got that message, and two, it was difficult to tell what version is installed when I check it anyways. Obviously, it was probably time to update the Gateway.
Based on your suggestion, I updated the Enterprise Gateway to version 14.16.6792.1 (August 2018), and restarted the service. (BTW, I'm very pleased to see how much more polished the Gateway interface is now since I last updated in March... I can see the version numbers now, and there seems to be more configuration options.)
After updating the Gateway, I attempted to refresh again via the Power BI Service, and this time it worked! I guess the on-premise Enterprise Gateway was out of date and was the root of the issue.
Thank you very much for the solution Gilbert!
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
59 | |
35 | |
27 | |
26 | |
24 |
User | Count |
---|---|
62 | |
53 | |
30 | |
23 | |
20 |