Forum Discussion
Embedding paginated reports error pop-up: Unable to render paginated report
We have identified the cause of the issue, which began occurring suddenly last week. After reaching out to Microsoft Support, this is the response we received:
"Issue:
Embedding paginated reports error pop-up: Unable to render paginated report
Analysis:
I have gone through the statement you provided. We assume that you are facing issue with Paginated report rendering.
We checked the issue internally and found that there is a known issue going on. When embedding a paginated report, it will render fine, but intermittently a pop-up might show up in the start of the embedding. User can close the pop-up to continue his experience regularly.
Our PG team is working on the issue and as a workaround they informed that user can close the pop-up and continue his experience regularly. We checked and the fix will be released in the third week of December 2024. We will inform you regularly if the fix release is preponed or postponed."
In short, this is a bug within a Microsoft product that they are aware of and are currently addressing. The fix is likely to be released by late December 2024.
Hi PowerNerd ,
Based on your statement, I think that even though there is a pop-up window displaying the error when loading the embedded paging report in the web, it still displays successfully after closing the pop-up window.
You can clean up the browser cache, as cached data might be causing the rendering error.
Please refer to below offical blog and follow the steps and try again.
For reference:
Embed paginated reports in your Power BI embedded analytics application - Power BI | Microsoft Learn
Please make sure the which kind of embed method you are using and follow the sample as below.
Embed content in your Power BI embedded analytics application - Power BI | Microsoft Learn
Best Regards,
Rico Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hello Anonymous,
I appreciate your response on this. However, we have already tried clearing the cache, using different browsers, switching between normal and incognito modes, and several other troubleshooting steps, but unfortunately, none of these have resolved the issue.