Error with Telerik Reporting and OpenAccessDataSource

1 Answer 9 Views
Report Viewer - WPF
almostEric
Top achievements
Rank 1
Iron
Iron
almostEric asked on 16 Oct 2025, 07:48 PM

After using Telerik reporting for over 10 years, with the latest update we are now getting this error when trying to print a report.

Looks like we now need to add something to our app.config file.

Would be cool if this were documented somewhere

1 Answer, 1 is accepted

Sort by
0
Ivet
Telerik team
answered on 21 Oct 2025, 11:25 AM

Hi Eric,

Thank you for the provided screenshot of the error.

The type Telerik.Reporting.OpenAccessDataSource is part of the Telerik.Reporting.dll assembly and is used to connect Telerik Reports to a Telerik Data Access Model.

You are encountering a new configuration requirement introduced in recent Telerik Reporting versions. Starting with the 2024 Q3 release (18.2.24.924), type restrictions were tightened for security reasons. Custom assemblies, such as those used in ObjectDataSource or OpenAccessDataSource, now need to be explicitly listed in your application's configuration file.

This change is a security measure to prevent unauthorized usage of assemblies within reports. Previously, your app.config did not need these customizations, but the updated version enforces stricter type checks.

Add an <AssemblyReferences> section under the <Telerik.Reporting> configuration in your app.config or web.config. List each required assembly by name. Here’s an example:

<configuration>
  <configSections>
    <section name="Telerik.Reporting"
             type="Telerik.Reporting.Configuration.ReportingConfigurationSection, Telerik.Reporting, Version=19.2.25.1001, Culture=neutral, PublicKeyToken=a9d7983dfcc261be"
             allowLocation="true"
             allowDefinition="Everywhere"/>
  </configSections>
  <Telerik.Reporting>
    <typeReferences>
        <add typeName="Telerik.Reporting.OpenAccessDataSource" assemblyName="Telerik.Reporting" publicKeyToken="a9d7983dfcc261be" />
    </typeReferences>
  </Telerik.Reporting>
</configuration>

The change and workaround are documented in the official release notes and configuration documentation:

If the information doesn't help you please send me a Trace log:

Looking forward to updates from you.

Regards,
Ivet
Progress Telerik

Your perspective matters! Join other professionals in the State of Designer-Developer Collaboration 2025: Workflows, Trends and AI survey to share how AI and new workflows are impacting collaboration, and be among the first to see the key findings.
Start the 2025 Survey
Tags
Report Viewer - WPF
Asked by
almostEric
Top achievements
Rank 1
Iron
Iron
Answers by
Ivet
Telerik team
Share this question
or