Forum Discussion
DM_GWPipeline_Gateway_MashupDataAccessError
Hello everyone,
I saw all the bugs like this one but didn't find a way to solve it yet.
In Power BI Desktop it refresh ok. Each time that I publish again in PBI online, it fails and the table is always changing.
This issue appear after we add Incremental refresh on one table, we took out the table (and chats with that data) but the issue continues.
Can some one help me please?
Erro na origem de dados: {"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"Information is needed in order to combine data"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.DataSources","detail":{"type":1,"value":"[{\"kind\":\"SQL\",\"path\":\"wptlis1sql01;Nice\"},{\"kind\":\"SQL\",\"path\":\"wptlis1sql01;Webtools\"}]"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.Reason","detail":{"type":1,"value":"PrivacySetting"}}],"exceptionCulprit":1}}} Table: Nice_Quality_Score.
25 Replies
You can find more information here: https://powerbi.microsoft.com/en-us/blog/privacy-levels-for-cloud-data-sources/
I Tried changing the privacy level but still facing the same issue, but now sometimes dataset is refreshed, and after sometime data refresh failed with the same error.
I am using postgres as my data source to the dataflow. And using dataflow to create dataset.
Data source error: {"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"The underlying connection was closed: An unexpected error occurred on a receive."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.Detail","detail":{"type":1,"value":"https://api.powerbi.com/powerbi/globalservice/v201606/clusterdetails"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}}],"exceptionCulprit":1}}} Table: AQI OIZOM_DEVICEDATA.
Cluster URI: WABI-US-EAST-A-PRIMARY-redirect.analysis.windows.net
Activity ID: c243b57d-3a6f-48b9-aa7b-6af9d1ce0e7f
Request ID: 408340f0-da90-a082-88f6-dbe3fc58ea53
Time: 2023-10-20 03:34:45ZThat points to data source or network instability.
What is the gateway version?
I'm using multimple table in a daset but getting this below error with one of the table, when I used to remove this table alone the dataset is refreshing succesfully. Why I'm getting error with one specific table - tried by changing all the datasources as per the suggestion but still no use. Please help!!
Data source error: {"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"ERROR [HY000] [Simba][BigQuery] (131) Unable to authenticate with Google BigQuery Storage API. Check your account permissions."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}}],"exceptionCulprit":1}}} Table:Hello,
I have the same issue now and were you able to fix this and how? exactly the same error code. Please share if you did and if you remember
This thread has a lot of suggestions that you can try.
Information is needed in order to combine data err... - Microsoft Power BI Community
Checking how you eventually resolved this
why doess it marked as resolved , when there is no solution ........... someone needs to address this from microsoft
hello , i have the same problem ,help please
I have faced same problem. But done manual refresh using refresh now option ,it will work properly . Anyone find premanent solution for this schedule refresh issue.
hi all,
I just tried to increase meemory used to refresh the report.Worked for me.
Open it via PBI desktopTry update the Cloud connections in the Gateway and cloud connections sections of the report.
Hey Rick
Been working through this with MS Support
In short the PBI On Premise Gateway doesnt support any Connection that has a Privacy Level = None.
MS Support showe dme an extract from online learn help pages. So while MS allow you to select None when you create a connection for the Gateway its not supported.
MS simply need to remove NONE from the drop down in the configuration and when that was suggested I was told to add an "Idea". Very frustrating when clearly its not an enhancement or feature we are asking for. Just a way to avoid people like us hours of debugging work.
Here is what I did and haven't had the same error return...
Yes you shouldn't have to do some of the things in these steps but are forced to to get it to work.
1. In PBI Desktop work through each of the Data Source Connections and ensure that you select a Privacy level. Public or Organisational. Use the same across all connections.
2. Publish your report
3. In PBI Service online, add Database connections for your report and ensure they are setup with the SAME privacy level as the report PBIX. All connections must have the same as the PBIX.
4. In you Scheduled Refresh configuration ensure the Data Source Connections from the Report are Mapped to the newly created Gateway Connections.
5. Performs your Gateway refresh.
Something else to mention..
In the PBI Desktop there is a Report option "Ignore Privacy Levels" in the settings for the Report.
This only applies to the PBI Desktop refresh. It is not referred to or used by the Gateway refresh.
So while you think you are telling PBI to ignore Privacy Levels, its the PBI Desktop only that will ignore them.
This is a very strange issue, as there are many suggested solutions that worked for different people.
I have been having the same issue, and has been resolved. I tried changing privacy levels as explained in other replies, also rebooted the windows server that has the gateway(latest version), then restarted the gateway but didn't work.
My solution: I simply redeployed the view that was causing this error after testing it in my QA environment, and just like that the report is now refreshing fine.Hi,
I got a similar error as below. I changed the privacy level, but I could not find any solution. I think the error is with the record, as mentioned. It is strange, because in the desktop is ok, but in the power bi service, I face this issue. I tried to remove some steps from my query, and it works, so I think the error is in a step of my query that uses a function. I haven't managed to solve it after hours. If someone has had a similar experience with a function, I would appreciate any tips you may have. many thanks
Data source error: {"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"We cannot convert the value \"[Record]\" to type List."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ErrorCode","detail":{"type":1,"value":"10277"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"Expression.Error"}}],"exceptionCulprit":1}}} Table: ACCA.
Cluster URI: WABI-NORTH-EUROPE-O-PRIMARY-redirect.analysis.windows.net
Activity ID: acbfee22
Request ID: b2ab10c3
Time: 2025-08-20 12:27:57ZYour error has a different cause. Read about Value.Is - then you can treat records as single item lists.
