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.
An unexpected error occurred
An unexpected error occurred
Timestamp: 2025-01-06T13:37:13.082Z
Root activity ID: ec9af266-950b-364a-d547-4123a2f4f86b
Session ID: 00001a0c773348a9aa7b93ade21e8b30
Tenant ID: 9a50eba8-7568-447a-bcb9-27a0d464aa80
Cluster: https://9a50eba87568447abcb927a0d464aa80-api.analysis.windows.net/
Report ID: null
Capacity ID: undefined
ReportViewerVersion: 2024.11.3.1699
3 Comments
Hi Anonymous ,
Based on the above information, this issue is complex which may need to collect log files for further troubleshooting. Since community support engineers don't have that access, I would suggest opening a Support Ticket. If you are a Power BI Pro or Fabric licensee, you can create a support ticket for free and a dedicated Microsoft engineer will come to solve the problem for you.
It would be great if you continue to share in this issue to help others with similar problems after you know the root cause or solution.The link of Power BI Support: Support | Microsoft Power BI
For how to create a support ticket, please refer to How to create a support ticket in Power BI - Microsoft Power BI Community
Best Regards,
Community Support Team _ Caitlyn- 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.