Forum Discussion
Helper IIIService refresh "unable to combine data" citing PrivacyError
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":"[Unable to combine data] Section1/Func_307376f2_af97_449d_9a2e_40916ed73b8d references other queries or steps, so it may not directly access a data source. Please rebuild this data combination."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.DataSources","detail":{"type":1,"value":"[{\"kind\":\"Folder\",\"path\":\"C:\\\\Users\\\\kahloutg\\\\\\\\Documents\\\\xlsx\\\\mind\\\\\"}]"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.Reason","detail":{"type":1,"value":"PrivacyError"}}],"exceptionCulprit":1}}}
It was all working fine all the way up to Sep 24. I wake up on Sep 25 and it doesn't refresh anymore, giving the above error.
The same file refreshes successfully in Power BI Desktop.
5 Replies
- collinq
Super User
Hi gk2go ,
You need to make sure that the privacy settings are the same in the desktop as they are in the gateway/the service. If they are different on any data source then this will happen.
I would appreciate Kudos if my response was helpful. I would also appreciate it if you would Mark this As a Solution if it solved the problem. Thanks!
gk2goThey are set the same on both ends, and have certainly not changed between Thursday and Friday.
- collinq
Hi gk2go ,
Does your data have a parameter in it? This thread had the same error and this was the solution:
This does appear to be a recent issue for a lot of folks though - the unable to combine data problem. I would also suggest creating an issue or a ticket as I have started seeing this problem popping up the last couple of days and perhaps Microsoft is not aware of the problem.
I would appreciate Kudos if my response was helpful. I would also appreciate it if you would Mark this As a Solution if it solved the problem. Thanks!
