Forum Discussion
Failed to open the MSOLAP connection. - PowerBI Embedded
Hi, the issue was related to RLS. There was a rogue space in the code, specifically where we defined the Role. Hopefully this is helpful to someone in the future.
Hi, the issue was related to RLS. There was a rogue space in the code, specifically where we defined the Role. Hopefully this is helpful to someone in the future.
Hi Can you please elaborate a little bit about this rouge space issue, since I am having the same
Failed to open the MSOLAP connection. - PowerBI Embedded
Issue
Just thought I would post how I resolved this issue as I didn't find it anywhere. (Potentially similar solution to the "rogue blank space")
I inhertied our reporting architecture and we use PBI Embedded service. One of the requirements is that we must have a role created on the report (RLS), however, the role name must be a specific word. In my case, I was adding the role name as "Subscription" whereas it MUST be "Subscriber". This wasn't documented anywhere so I only figured it out by reviewing other reports.
debenaireHelper I
hi All thought I would contribute here. I had the same issue and it turned out to be linked to RLS and composite model. Effectively I belive I tried to use direct query on some tables to be used for RLS. To resolve the issue I removed the tables from my model, even though they were now in import mode and reimported them. This resolved the issue!
