New to Telerik Reporting? Download free 30-day trial

Resolving PDF Rendering Format Not Available in ASP.NET Core Applications

Environment

Product Progress® Telerik® Reporting
Target Framework .NET 8+

Description

After upgrading an ASP.NET Core application to .NET 8 the PDF rendering format becomes unavailable. The error message encountered is Telerik.Reporting.Processing.RendererNotAvailableException: PDF rendering format is not available.

Cause

The root cause of the issue is missing or incorrect references to Telerik Reporting assemblies, necessary for PDF rendering. This problem may arise from using assembly references directly instead of NuGet packages, using .NET Framework assemblies in a .NET project, or missing sub-dependencies. Additionally, conflicts with certain NuGet package versions, such as System.Configuration.ConfigurationManager version 8.0.0, can trigger this error.

Solution

  1. Use Telerik Reporting NuGet Packages: Instead of directly referencing assemblies, install the Telerik.Reporting NuGet packages which includes the PDF rendering extension. For instructions on setting up the Telerik private NuGet feed, refer to Adding Telerik NuGet Feed to VS with Package Manager or CLI - Telerik Reporting.
  2. Correct Assembly Locations: If using assembly references, ensure that the Telerik Reporting assemblies are sourced from the appropriate directory for .NET applications, typically found in C:\Program Files (x86)\Progress\Telerik Reporting 2024 Q1\Bin\netstandard2.0.
  3. Include All Sub-Dependencies/Packages: Manually verify that all necessary sub-dependencies are included in the project. Detailed requirements can be found in the Using Telerik Reporting with .NET 6+ or Standard article.
  4. Address Dependency Conflicts: If the System.Configuration.ConfigurationManager package version 8.0.0 is present, downgrade it to version 7.0.0 as it is known to cause the aforementioned error. This package may have been installed as a sub-dependency by other packages, such as Microsoft.Data.SqlClient.

See Also

In this article