Forum Discussion
New paginated report authoring experience - Unexpected Error
We are attempting to use the new Paginated Report experience on 6th Jan 2025
The screen is starting the appropriate web page and I can briefly see the data model and empty table, but then it just stops with the following.
Is anyone else seeing this issue?
We finally managed to fix this issue by making changes in ZScaler.
The paginated report issue seems to have been resolved after the changes made in ZScaler. The issue we were seeing was that after we clicked the option for to create paginated report, the Zscaler logs showed that it was quarantining the PDF files which prevented the reports from generative. I worked with Zscaler on a rule for the Paginated reports to allow the pdf files to run that would allow it to bypassed the quarantine action we were seeing.
13 Replies
bradsyMicrosoft Employee
Hi Daryl - Can you enable the browser F-12 feature and check the network traces and see what is failing? It could be possibly fetching the data or something else is blocked by a firewall or permissions to something. And looking at the Cluster URI, this is a private link scenario. It also could be outboud connectivity is not enabled or using a semantic model with private links is not allowed. https://learn.microsoft.com/en-us/fabric/security/security-private-links-overview#power-bi
Thanks bradsy - I have opened a support ticket and provide them with the Network traces. Please note:
> it appears to successfully connect to the Semantic Model. I can see the table and columns appear briefly on right hand side of the screen before the unexcepted error appears.
> the paginated report does not work in any workspace premium, trial or pro, and Privatelink is not enabled.
v-sgandrathiCommunity Support
Hi Anonymous,
If you’ve raised a ticket, please confirm if it’s acknowledged and whether you’ve received any updates or a resolution from the support team.
Thank you for being a part of the Microsoft Fabric Community.
- v-sgandrathi
Hi Anonymous,
Thank you for reaching out to the Microsoft Fabric Community forum.As bradsy mentioned the response is accurate and will address your issue.
I hope this suggestions give you good ideas, If you have any further questions or updates regarding your issue, feel free to ask, and we will look into that.
If answer meets your requirements, please give us Kudos and consider marking Accepting it as a solution to guide other members in finding it more easily..
Thank you for being a part of the Microsoft Fabric Community Forum!
SaiTejaTalasilaSuper User
Hi Anonymous ,
Don't use preview features in your production reports. There is no guarantee that the feature will be permanently available.
Ex-quick insights -it will be no longer available, due to performance issues they are removing that feature.
Thanks,
Sai Teja
Thank you, SaiTejaTalasila, I understand this is preview feature, so all our Production Paginated Reports were created using Report Builder. The point is to allow Citizen Developer to self-service using this feature. This reduces the need for them to get a Developer VM with the software installed. Unfortunately, no one can use the feature because it crashes immediately after connecting to the Semantic Model. I gather that you can use the preview feature without seeing this "unexpected error".
OliverOHelper III
Hi, did this issue get resolved? I am having the same problem
Hi OliverO - not yet. I have ZScaler support ticket to help identify the root cause. An initial fix did not work - it had the opposite affect.
- OliverO
thanks Daryl!
We finally managed to fix this issue by making changes in ZScaler.
The paginated report issue seems to have been resolved after the changes made in ZScaler. The issue we were seeing was that after we clicked the option for to create paginated report, the Zscaler logs showed that it was quarantining the PDF files which prevented the reports from generative. I worked with Zscaler on a rule for the Paginated reports to allow the pdf files to run that would allow it to bypassed the quarantine action we were seeing.
Hey Daryl - what changes did Zscaler make in your environment? We found this issue to be related to Chrome and LocalNetworkAccessRestrictionsEnabled. Chrome pushed local network access restrictions in version 142+ which causes issues with paginated reports in PBI. The only workaround we found was to either stay on Chrome v141 or set LocalNetworkAccessRestrictionsEnabled to false in a GPO. Chrome DEVs are aware of the issue and expect to have a fix at some point. If there is something we can do on the Zscaler side let us know. Here is the link to the Chrome DEV page:
https://issues.chromium.org/issues/467417114
https://issues.chromium.org/issues/467085904
I just checked back on both DEV pages and it appears the fixes have pushed to v146 and/or v147 of Chrome. I'm going to disable the GPO for a subset of machines and set [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\LocalNetworkAccessIpAddressSpaceOverrides]
"1"="100.64.0.0/10=public"Confirmed this is fixed with the latest Chrome v146 AMDX files - Update your GPO:
set LocalNetworkAccessIpAddressSpaceOverrides to enabled add 100.64.0.0/10=public (whatever your Zscaler clients are set to)
set Allow Local Network Access (LNA) requests in subframes to enabled
Need both
