Our Development Team is currently evaluating Aspose.Words for purchase under a 30-day trial. We are hopeful we can use Aspose.Words to provide a specific client system requirement for this project and many others. However, we are running into a hard stop error when rendering *.rdl reports with the Aspose.Words DOCX feature and therefore cannot validate the product works.
Environment:
We are currently using Aspose.Words Version 25.8 on Microsoft Power BI Report Server 15.0.1118.134 running on Windows Server 2022 Datacenter Azure Edition. Apose 25.8 was installed following the “manual installation” instructions provided on the Aspose website.
Test Scenario:
We login into our Power BI Report Server and launch a *.rdl report.
We enter any required report parameters and “view the Report” which renders it in the browser.
We then click the Aspose for DOCX feature newly installed on the Power BI Report Server under the “Save” menu option.
We then receive a generic error in the browser that states “Report Server Error - For more information about this error navigate to the report server on the local server machine, or enable remote errors.”
We then check the server event viewer application logs to find a corresponding Power BI error and subsequent *.log we find that:
“Microsoft.ReportingServices.ReportProcessing.UnhandledReportRenderingException: An error occurred during rendering of the report. —> System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection.”
Is Aspose aware of anything that may cause this error OR any configurations we could change that would allow us to continue testing and evaluating the product?
Thank you for reaching out! It sounds like you’re encountering a frustrating issue while trying to render *.rdl reports using Aspose.Words on Power BI Report Server. The error message you’re seeing, specifically the “Index was out of range” exception, typically indicates that there might be an issue with the data being processed or a configuration setting.
Cause: The “Index was out of range” exception often arises from missing or incorrect report parameters, complex report designs, or outdated software versions.
Solution: Here are some steps you can take to troubleshoot and potentially resolve the issue:
Check Report Parameters: Ensure that all required parameters for the report are being passed correctly. Missing or incorrect parameters can lead to rendering issues.
Update Aspose.Words: Since you’re using version 25.8, consider updating to the latest version of Aspose.Words. There may have been bug fixes or improvements that could resolve your issue.
Review Report Design: Examine the design of the *.rdl report. Look for any complex expressions or data sources that might be causing the rendering to fail. Simplifying the report can help identify if a specific element is causing the issue.
Enable Remote Errors: As suggested in the error message, enabling remote errors in the Power BI Report Server can provide more detailed information about what might be going wrong. This can help in diagnosing the issue further.
Check Event Viewer Logs: Monitor the application logs in the Event Viewer for any additional errors or warnings that might provide more context about the failure.
Next Steps: If these steps do not resolve the issue, please consider reaching out to Aspose support with detailed logs and the specific report design. They may have additional insights or solutions.
I hope this helps! Please let me know if you have any further questions or need additional assistance.
@zachajiliti
Thank you for your feedback. We appreciate your interest in our service.
We are currently using Aspose.Words version 25.8 on Microsoft Power BI Report Server.
Can you provide additional information about the files you are using? In the Aspose.Words.ReportingServices.dll file properties, what versions of AW and RS are specified? The string in the file properties looks like “Aspose.Words for Reporting Services (RS2019, AW 25.8).”
We log in to our Power BI Report Server and launch an *.rdl report.
Please provide the problematic RDL report that allows us to reproduce the issue.
We then check the server’s Event Viewer (Application) logs to find the corresponding Power BI error, and in the subsequent *.log file we find that:
Also please, post the full error text that occurs.
This website advised “Sorry, the file you are trying to upload is not authorized (authorized extensions: jpg, jpeg, png, gif, zip, pdf, docx, 7z)” when I try to upload an *.RLD or *.log file from the server. I have copied/pasted each into a DOCX to side-step this deficiency.
We are currently investigating the *.rdl file to determine if there are any specific configurations that lead to successful rendering versus failure. If and when we isolate a specific condition we will respond here with an update.
Of course, any insight you could provide from your side would be greatly appreciated!
Hi @alexey.noskov@Sokz , do you have any updates regarding the resolution of the issue with these reports when exporting to ASPOSE DOCX and the mentioned error?
@zachajiliti
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): WORDSRS-352
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
@zachajiliti The issue is currently in the queue for analysis. We will keep you updated once the issue is resolved or we have more information for you. Please accept our apologies for your inconvenience.
