Dashboards Error - loading blocked by failures with other queries

Azure / CCOInsights

Welcome to the Continuous Cloud Optimization Power BI Dashboard GitHub Project. In this repository you will find all the guidance and files needed to deploy the Dashboard in your environment to take benefit of a single pane of glass to get insights about your Azure resources and services.

https://aka.ms/CCOInsights/videos

MIT License

717 stars 209 forks source link

Dashboards Error - loading blocked by failures with other queries #271

Closed matthansen0 closed 2 years ago

matthansen0 commented 2 years ago

First, I looked through all the other closed issues, including https://github.com/Azure/CCOInsights/issues/215, and I still get this issue.

Screenshots

I have my security and privacy settings configured as described:

I also have my connector stored like is described:

Paused OneDrive too:

I validated that the Connector is registering in Power BI as well:

I've tried this against my MSDN tenant, PayGo Tenant, and EA Tenant on a Windows 11 machine that's domain joined, one that's Windows 11 Home, and from a Server 2016 Azure VM all with the same errors. The dashboard in question is Infra, but Governance throws a similar error.

Brianbla commented 2 years ago

I happen to working on this same error with another user using the Infrastructure dashboard. There are 4 issues related to this error but the resolution was for the Governance dashboard - https://github.com/Azure/CCOInsights/issues?q=is%3Aissue+%22Loading+blocked+by+failures+with+other+queries%22

User PowerBI and file settings are confirmed correct according to the docs as you posted above.

Someone has already started a discussion regarding this error.

@matthansen0, I had this error before for Governance: #148 , the resolution was getting a new mez file as mine appeared to be corrupted.

matthansen0 commented 2 years ago

That's very interesting. When I git clone the repo I get a different hash of the .mez compared to when I download the raw file from a browser. That solved my issue. Maybe we should post the hash of that connector?