Forum Discussion
Embedded visual errors - Failed to move the data reader to the next row
Hi jkeizer ,
Is this still a problem? Is the error not reported in Power BI Desktop? Have tried clearing the browser cache? Has someone made some changes to the report?
Please pay attention. DirectQuery will be slower when dealing with large volumes of data. Thus, this error is possible due to the high data volume.
How to Get Your Question Answered Quickly
If it does not help, please provide more details.
Best Regards
Community Support Team _ Rongtie
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi Anonymous ,
Yes it's still a problem. No errors in desktop or service when I view it in the workspace. Only in the embedded app, it was working without issues for months before yesterday. I have tried clearing the browser cache and I don't think it's related to data volumes because even simple slicers do not load anymore. There is RLS on the report but no changes related to that were made, and when testing RLS in desktop it still works.
Update:
We've had a very similar issue last year, back then it turned out to be a Microsoft issue. Another user reported this at the time:
Embedded reports built over multiple XMLA datasets... - Microsoft Fabric Community
I also checked the Embedded Playground (because last year the reports were fine there) and they load without any issues.
Best,
Joery
Hey Joery!
Could you please share the findings and solution of this issue, we are facing this weird issue occasionaly.
Most of the time, report is working fine but once in a while (mostly once in a fortnight we encounter this).
More info: we are using common dataset for many reports with live connection to Dataset.
Dataset refresh once a day (import mode), issue seen after scheduled refresh (whenever seen).
Issue seen with RLS roles only, not when RLS role not involved (Never seen in Desktop).
Gets resolved automatically after few hours.
Hi arjunislearning. I'm afraid I don't have any helpful details. Microsoft support was still investigating when the issue resolved itself (after 2.5 weeks). I still believe it was an error on Microsoft side but they were not aware of any ongoing issues.
It has been a little while now since your last comment. I was wondering if you had gotten anything back on this or a resolution? Thanks in advance!
