Looking to evaluate Aspose.PDF for Report Services, and need help which version works with my OS. We are on Windows Server 2019 with .Net framework 4.8. Its not clear to me which version of the dll will work for me.
@leonid.foksha
Thank you for your question. After checking with our development team regarding your setup (Windows Server 2019, .NET Framework 4.8), here is the detailed answer:
1. The Latest Version (25.5)
The latest release is Aspose.PDF for Reporting Services 25.5.0 .
https://releases.aspose.com/pdf/reportingservices/new-releases/aspose.pdf-for-reporting-services-25.5.0/
However, this version is compiled for .NET Framework 4.8.1 .
- Will it work? It will only work on your Windows Server 2019 if you have .NET Framework 4.8.1 installed.
- Supported Versions: This version officially supports Microsoft SQL Server 2016/2017/2019/2022 Reporting Services and Power BI Report Server.
2. The .NET 4.8 Issue
We understand that your server currently has .NET Framework 4.8 (not 4.8.1).
- There was a period where we re-targeted our main library from 4.8.1 back to 4.8 specifically to support certain operating system configurations (including some cases involving Windows Server 2019).
- Therefore, the latest version (25.5) may not work “out of the box” on a clean .NET 4.8 installation.
3. Recommendations & Next Steps
You have a few options to proceed:
- Option A: Update your server (Recommended for testing). Install .NET Framework 4.8.1 on your Windows Server 2019. This is a direct update. After that, you can try the latest version 25.5 . It has the best chance of working immediately.
- Option B: Test the current version. You can try installing Aspose.PDF for Reporting Services 25.5.0 on your current .NET 4.8 setup. There is a chance it might work, but we cannot guarantee compatibility in this specific configuration.
- Option C: Request a rebuild (If Option A is not possible). If you cannot update to .NET 4.8.1 and the test fails, we can create a ticket to rebuild the latest library specifically targeting .NET Framework 4.8 . Please let us know if you need us to proceed with this. (This is not a promise to do it in a short time, it will only create a task for the developers)
Thank you for your suggestions, we decided to update our server to Windows Server 2025 with .NET Framework 4.8.1 and with 25.5 and we are on Power BI Report Server 1.24.
We are now getting a different issue when we try to run the report.
Log Name: Application
Source: ASP.NET 4.0.30319.0
Date: 3/17/2026 9:59:56 AM
Event ID: 1325
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: *************************
Description:
The description for Event ID 1325 from source ASP.NET 4.0.30319.0 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Failed to initialize the AppDomain:ReportServer_PBIRS_0
Exception: System.Web.HttpException
Message: Could not load file or assembly ‘ReportingServicesWebServer, Version=15.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91’ or one of its dependencies. The parameter is incorrect. (Exception from HRESULT: 0x80070057 (E_INVALIDARG)) (C:\Program Files\Microsoft Power BI Report Server\PBIRS\ReportServer\web.config line 17)
We have the original copies rsreportserver.config and rssrvpolicy.config files and if we put them back the reports run on the report server with no other changes.
The only change in rsreport server.config is added line below in Render section
lt Extension Name=“APPDF” Type=“Aspose.Pdf.ReportingServices.Renderer,Aspose.Pdf.ReportingServices”/>
The only change in rssrvpolicy.config is added block in CodeGroup section at the end
lt CodeGroup class=“UnionCodeGroup” version=“1” PermissionSetName=“FullTrust” Name=“Aspose.Pdf_for_Reporting_Services” Description=“This code group grants full trust to the AP4SSRS assembly.”>
lt IMembershipCondition class=“StrongNameMembershipCondition” version=“1” PublicKeyBlob="00240000048000009400000006020000002400005253413100040000010001005542e99cecd28842dad186257b2c7b6ae9b5947e51e0b17b4ac6d8cecd3e01c4d20658c5e4ea1b9a6c8f854b2d796c4fde740dac65e834167758cff283eed1be5c9a812022b015a902e0b97d4e95569eb8c0971834744e633d9cb4c4a6d8eda03c12f486e13a1a0cb1aa101ad94943236384cbbf5c679944b994de9546e493bf " />
lt /CodeGroup>
Line 17 in web.config file is
lt add assembly=“ReportingServicesWebServer” />
The bold lt is the less than symbol which editor removes.
We did not make any changes to this config file recently.
Any suggestions on what we can try.
@leonid.foksha
I asked the developers who work directly with this product.
Is this all compatible?
Aspose.Pdf for Reporting Services 25.5 with Power BI Report Server 1.24 and .NET 4.8.1 on Windows Server 2025.
and asked for comments.
Here’s the answer.
Yes, this configuration is fully compatible.
The error the user is reporting—I’m not sure if it’s related to our extension; he doesn’t need ReportingServicesWebServer to work.
But to verify, the user can remove the extension and its associated entries from the config files, leaving the remaining changes, and try running it.
And it’s best to install the extension, of course, via the MSI installer. If you installed it manually, have them follow the instructions, carefully look at the steps specifically for PowerBI, and verify that they did everything correctly.
We got it configured and running and generating PDFs of our reports. How do we enable the rendering of accessible PDFs?
For the Microsoft renderer we added this
ltConfiguration>
ltDeviceInfo>
ltAccessiblePDF>Truelt/AccessiblePDF>
lt/DeviceInfo>
lt/Configuration>
lt/Extension>
The bold lt is the less than symbol which editor removes.
To force every PDF to be accessible, do you have similar configuration code that we can add in the rsreportserver.config file.
@leonid.foksha
I asked a colleague who is directly familiar with the product, he gave the following explanation.
All available configuration options are described in the documentation. If something isn’t there, it’s not supported by the extension. If “Accessible” means PDF/UA-1, then it seems there’s currently no support for that format. But it’s best to double-check.
And if they ask for an implementation, have them immediately provide an example of what Microsoft is doing with Accessible, using a simple report.