Error fetching data for this visual

[SharpPoint]

Hi.
We have a PowerBi /workspace that has access permissions defined by an Azure security group.  The same Azure group has access to the Semantic model and the data warehouse/tables that are used in the semantic model.  When users view the PowerBi  (all are members of the Azure security group), it works flawlessly for some, while others get the Error fetching data for this visual error.  There does not seem to be a pattern to why some users  cannot view the PowerBi. We have tested with various browsers and in congnito browsers with no effect.

Occassionally a user will get this error message (when viewing the PowerBi for the first time),

A connection could not be made to the data source with the Name of '{"protocol":"analysis-services","address":{"server":"powerbi://api.powerbi.com/v1.0/myorg/NameHere","database":"NameHere"},"authentication":null,"query":null}

If they close their browser or refresh that will either fix the issue or result in the above Error Fetching Visual issue. 

Any ideas on what i could check?

[dknash]

For anyone with a similar issue, we had an "overview" report with row level security that was sourced from multiple workspaces that was giving this error. When looking at the cloud connections, I noticed that there was a connection to a report in our DEV workspace (no end user access) that had the same name as the intended report in our PROD workspace (end users have access), and that was the cause. So the overview report had either been built using the DEV report connection and never switched over, or the report had been inadvertantly set up to use the DEV report instead of the PROD report.

I wouldn't expect this to be the case in every situation, but we were stuck for a while trying to figure this out, so I figured that it could help. The gateway/cloud connections do seem to be the right direction to pursue.

[SharpPoint]

Update on this.  Looks like Microsoft rolled out an update in January .  Our client version in the cloud is now 2412.3.22264-train.  The visual now works.  We did not have RLS enabled, but we have restricted tables to specific groups. These groups are also the same ones that were given access to the workspace.    Just wondering if anyone else who might have had the same issue and their tenant is in Central Canada if they notice the issue has been resolved for them?

[ChandraT]

Hi,

Were you able to resolve the issue or did you get any feedback from Tech Support.

Thanks

[SharpPoint]

still working on it.

[SharpPoint]

I have a ticket open with MS support. No update yet.

[Sultanista]

We have same issue. It appeared when we implemented RLS. User have access to the dataset, they are in the group coresponding to RLS role . 
Once we removed the RLS they can see data again. 
Any idea how to resolve it?

[powerbi532]

I am experiencing the same issue. Have you found a solution?

[SharpPoint]

We do not have a solution yet, but i do have a ticket open with fabric support.  

[Anonymous]

Hi, @SharpPoint 

In your description, some users can see the data normally, while some users will get an error, do the users who can see the data normally have a role in the workspace? For example Admin, Contributor, Member, Viewer, is there any difference in the permissions of these users?

And what connection mode are you using to connect to the data source?QirectQuery?Or Live Connection?

The error message you provided shows ‘authentication’:null, which could mean that the authentication information is missing or incorrectly configured. Please ensure that the user has the appropriate permissions for access and that authentication is configured correctly.

If you are using Live Connection, you need to use Map User when creating a gateway connection:

Here's the official documentation, hope it helps:

Manage SQL Server Analysis Services data sources - Power BI | Microsoft Learn

I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Fen Ling,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[SharpPoint]

Hi.
The users all belong to a single security group in EntraID.  The group has viewer access to the workspace and read/select on the data in the data warehouse.  So far we've been unable to determine any permission difference between the users who can't view the visuals and the users who can view the visuals.

[pborah]

Hey @SharpPoint , we had a similar but not the same issue recently. Check your data gateway and its proxies. If you have more than one proxy for your data gateway, check the settings and certificates for each of them. Could be a mismatch issue. When your end users try to access the report they are directed by any available DG proxy. If one proxy has cert auth disabled and the other has it enabled and there's a mismatch, your users will experience an access issue intermittently depending on which proxy they are routed by. You may need to get in touch with your IT team for this.

[SharpPoint]

Thanks for the suggestion, but in this case the data is already sitting in a fabric datawarehouse, so i believe the gateway is out of the question?   

The powerbi report and semantic model used by the report are built off the DW tables and exists in a different workspace from the data warehouse.  The same Azure group  is used to define permissions.
I have confirmed users that exhibit the issue can access existing powerbi reports in fabric.  It is always the same users who exhibit the "Error fetching data for this visual" error.  More of a permanent error for these users.

I should also mention that users with the free fabric license or power bi pro license see the error.  The workspaces and data warehouse sit on a capacity license.

[pborah]

I see. It might be worth it to inspect the AD group itself in that case or even whether those users have the free license to be able to view PBI service reports. That is unless you've already gone that route. Goodluck! Curious to see what the resolution would be.