Issue: can't access previously created lakehouse from Power BI persona UI. Clicking on New report --> Pick a published semantic model --> select model, gives the error below: Underlying Error: Capacity operation failed with error code CannotRetrieveModelException Activity ID: d25b479d-6c03-4aee-b6d8-ff034ba450e8 Correlation ID: cb485f01-ca36-a07f-fd98-3610436063fb Request ID: f4dac7ef-cddf-097c-bb38-1f47336bd5e2 Time: Thu Feb 15 2024 04:08:11 GMT-0500 (Eastern Standard Time) Service version: 13.0.22638.74 Client version: 2402.1.17926-train Cluster URI: https://wabi-canada-central-redirect.analysis.windows.net/ Again, what on earth is going on???

That wasn't it. Was on a call with MS Support, it's internal bugs they are working on and hopefully, everyone cross fingers now, they will be fixed at some point in future.

BUG::semantic model inaccessible when creating a report with Power BI persona

18 Replies

Anonymous
Not applicable
1 year ago
This is still an issue - you just can't create a Fabric PowerBI report from a Fabric Warehouse semantic model.
I'm stunned MS can release this garbage and charge people for it. They clearly just don't bother performing the most basic tests or basic features
- jpelham
  Advocate I
  1 year ago
  We did end up resolving this issue. After reaching out to Microsoft, we found that we needed to Whitelist some IPs. I totally get your frustrations though!
  
  Add Fabric URLs to your allowlist - Microsoft Fabric | Microsoft Learn
  Add Power BI URLs to allowlist - Microsoft Fabric | Microsoft Learn
user518520
Frequent Visitor
2 years ago
very similar issues here - any update on this ?

tried work around to connect as SQL Analyis services - and no error pop ups. like

"'x-ms-root-activity-id', not found in Http response that was returned by Azure Analysis Server"
"Failed to connect to URL https://api.powerbi.com while attempting to call cluster resolution"

so April edition of PowerBI desktop still has problems
GilbertQ
Super User
2 years ago
Hi Element115

Can you please confirm that your capacity is still running? It could be quite possible that it is has been paused.
- Element115
  Memorable Member
  2 years ago
  That wasn't it. Was on a call with MS Support, it's internal bugs they are working on and hopefully, everyone cross fingers now, they will be fixed at some point in future.
  - Kryt0n
    Advocate I
    2 years ago
    Have you received any update on this? I'm seeing the same error so curious if you had it resolved
- Anonymous
  Not applicable
  2 years ago
  Hi Element115
  We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. Otherwise, will respond back with the more details and we will try to help.
  Thanks
  - Element115
    Memorable Member
    2 years ago
    Sorry for the late reply, but I was pulled from testing Fabric to another urgent project last week. I tried again today, that is to say, connecting Power BI Desktop to a Fabric semantic model data source, in this particular case, a lakehouse containing all the Dim and Fact tables.
    
    Result: no more error message, but a UI that does nothing after selecting the data source and greys out almost all menu options. Here are the screenshots.
    
    And this is what it looks like after clicking Connect. The dialog eventually goes away, but nothing happens, and the options in the previous screenshots remain greyed out. You can't even create a blank query or enter data manually to start an instance of Power Query Desktop. Only option at this point is to close the report, and launch PBI Desktop again.
- Element115
  Memorable Member
  2 years ago
  Sorry for the late reply, but I was pulled from testing Fabric to another urgent project last week. Re your suggestion, I don't know how to do that. Also, I don't have Azure admin privs.
jpelham
Advocate I
1 year ago
Has anyone found a solution to this yet? We are having the same issues in Power BI Desktop when we try to connect to a lakehouse, semantic model, or an endpoint. No tables end up loading and most of the options are greyed out. We also get the same error as the original poster when in the service.
- Element115
  Memorable Member
  1 year ago
  I did a quick test and with PBID Version: 2.137.1102.0 64-bit (October 2024) and it does work if you select a lakehouse and then its SQL endpoint. Haven't tested with the other data sources in the dropdown menu.
  - jpelham
    Advocate I
    1 year ago
    Thanks for checking. When I attempt that method I get a handshake error. We are running an older version of Power BI Desktop, so I will have to look into that. Part of our issue is within the Power BI app though, so I'm suspecting there is something else going on that is unrelated to the version of Power BI destop.
    
    Thank you for the response!