12-14-2018 01:12 PM
We are experiencing a bug where periodically Q&A on Dashboards in the Power BI Service will stop working until we turn Q&A off and then back on again on the dataset we are querying.
Our dataset uses an Analysis Services live connection.
When it stops working, I opened Chrome DevTools to inspect what network traffic is happening and found a lot of 500s when calling out to https://wabi-us-north-central-b-redirect.analysis.windows.net/explore/interpretation/interpret/.
The request looks like this:
The error response is simply:
Successful requests against our other dataset include much more data in the "Spans" property on the request.
I know that a Live Analysis Services Connection Q&A feature for Reports just got pushed out and I'm wondering if that has anything to do with it. We did try out the Preview feature for one of our datasets (but not the one that is failing). Unless it pushes changes at the server level, we don't think it would have to do with that.
I've opened a ticket and will post here if there is a resolution, but wanted to see if anyone else has run into this.
12-15-2018 03:15 AM
Just Maneged to fix the issue thanks to Microsoft Support.
Befor publishing your report with power bi desktop you need to flag Enable Q&A Live Connect in Files > Options > Preview Features as in the screenshot below
12-21-2018 12:11 PM
Unfortunately this did not solve our issue. We even went as far as to create a brand new workspace, publish brand new reports and datasets live connected to the same Azure Analysis Services server, and publish a brand new app, all with and without the Live Q&A Preview feature enabled, but we get the same problem after an hour has passed.
12-26-2018 11:13 PM
Maybe you can submit a support ticket to get better support, it is free for pro and above licenses.
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
For learning resources/Release notes, please visit: | |
12-27-2018 02:18 PM
I have a support ticket open as well. I saw that the support team is aware of this issue and has a fix coming in est. 1/5 EOD. Will follow up on this post if that does not resolve the issue to keep anyone else affected updated.