Forum Discussion
Refresh error: Reason: PrivacySetting - "Information is needed in order to combine data"
Hello,
Since beginning of this week a bunch of our reports have started to fail out of the blue. They have worked perfectly fine for the last 6 months but suddenly can't refresh with below error:
Underlying error message: Information is needed in order to combine data
Microsoft.Data.Mashup.MashupSecurityException.Reason: PrivacySetting
Cluster URI: WABI-NORTH-EUROPE-redirect.analysis.windows.net
I have already read the other posts on this Community about this error and thus chaning Privacy settings to "None" on both Gateway sources as well as within Report Data source settings (as well as setting Report to "Always ignore") fixed it for SOME reports but not all.
One report specifically where I am trying to merge OData-Connection to Sharepoint 2010 with some Excel files on a company network drive. I can open the .PBIX file and Refresh perfectly fine, but when trying to refresh the published Dataset it fails with above error.
I am all out of ideas - please help!
Hi Anonymous and everyone else.
I think I have narrowed the changes of Privacy Settings in Gateway data source list down to the launch of Dataflows which happened same week.
The way Dataflows currently work has some unwanted sideeffects on Gateway Data source settings. If I add a Dataflow from Source A it will automatically change Source A privacy settings to "None" in the Gateway settings.
If I then change Source A back to "Organisational" in my Gateway settings my Schedules Refresh works again. Untill next time I go and fiddle around with a Dataflow from Source A resulting it to change back to "None" in Gateway settings.
... in addition, let's say you don't have a Source B in your Gateway source list yet. The moment you add a Dataflow from Source B it will automatically add Source B to your Gateway source list resulting in potentially unwanted sources in the Gateway....
17 Replies
- AnonymousNot applicable
Hi
Unfortunately I have the exact same issus. Started this week as well with no changes to the dataset at all. Has been running smoothly for months. Tried all the same and the service is also located in NorthEurope. My sources are on prem tables and azure db tables.
Hope there is a solution for this soon. Maybe the november gateway will fix it, but qiute critical that reports suddenly fails when microsoft is releasing updates (which is what I suspect has happened)...
- v-frfei-msftCommunity Support
Hi Mardin,
Could you please update your Power BI desktop to the latest version and try to publish the report to different workspace and renaming the PBIX as well? If the error still occurs, kindly porvide the Fiddler trace to me.
Regards,
Frank
- MardinAdvocate IV
Update: After a chat with Customer Support I tried to change ALL Data sources on the Gateway to "Enterprise" privacy setting as well as changed all data sources on all reports that go trhrough the Gateway to "Enterprise" as well.
It seems to function now - fingers crossed!
- AnonymousNot applicable
Nearly all of our production reports failed at this same time too with this same error...its almost like just this week the privacy setting feature started working as intended... Why no notification from Microsoft if they are going to make production changes that have brought many peoples reports down with no insight into how to fix???
- AnonymousNot applicable
Hi,
We recently started getting this error for one of our report refresh. I read all the comments and tried all the possible ways to make this work but, no luck.
I have set all the permissions to Organisation level. For me it is giving the error for Adobe Analytics. Following is the error snapshot. Before setting the permission it was giving the following error
After setting the privacy level now I am getting following error:
Can anyone please help me with this. I have tested all the connections on Power BI desktop and everything is working fine. But this error starts after publishing the report and try to refresh the dataset.
Please let me know if anyone have resolved this issue. Thanks in advance!