Report designer/server/viewer version compatibility

[Nick]

Suppose:

• We have a report, designed using the stand-alone designer, version A.
• This is being rendered by a report server, version B, to a REST endpoint.
• This is being downloaded and viewed with the WPF desktop client, version C.

then my question is: what is the compatibility between A, B, and C for different Telerik reporting releases?

Or,

• When do I need to update my report definitions as I update the server?
• Do I need to expose multiple report server end points with different versions for the clients to connect to (since we can't update ALL the clients at exactly the same time as the server)?

Any advice here most welcome.

Thanks,

Nick.

[Silviya]

Hello Nick,

The TRDX file contains the report XML definition with specified schema version based on the used Telerik Reporting version. 

Report that is created or modified with a newer version (creating report with the Standalone Designer) cannot be processed by the older version (Telerik Report Server). When you modify the report in Standalone designer of the newer version, the XML schema of the report will be updated. Designer of the older version is not able to read the updated schema and will show an error "Cannot read a document with the specified schema.." .

The same applies to the scenario between Report Server and the other machine which should preview the report in a report viewer. So, in order to successfully work with different versions of Telerik Reporting and Telerik Report Server, version C must be the same or higher than B, and B must be the same or higher than A.

For more specific suggestions/recommendation please specify the A, B, C versions with the actual ones.

Regards,
Silviya
Progress Telerik

[Nick]

Thanks for this. So we need to ensure, in general, that version (report designer) <= (report server) <= (report client).

That's not unexpected, so glad to have it clarified.

[Nick]

Resurrecting this, I've just upgraded our report viewer to 2020.1 SP 1, with the report generator staying at 2017.
This works fine for some reports, but for others I'm seeing the message:

"Cannot read a document with the specified schema: http://schemas.telerik.com/reporting/2017/3.0.
You might be using an older version of the product."

Any idea under what circumstances this might happen, and if there is any way to fix it so the reports can be viewed?

Thanks.

[Nick]

Additional clarification: the "http://schemas.telerik.com/reporting/2017/3.0" namespace is present in the action-documents request to the server, which returns a serializableReportSource XML containing this namespace. So the compatibility issue may be in loading this.

[Katia]

Hi Nick,

I will post my reply from the support ticket that you opened on the same question in case any other community member experiencing the same issue.

"XML schema http://schemas.telerik.com/reporting/2017/3.0 was introduced with version 11.2.17.913 which is older than version 11.2.17.1025. The error message "Cannot read a document with the specified schema: http://schemas.telerik.com/reporting/2017/3.0." indicates that the project that renders reports references the version of Telerik Reporting older than 11.2.17.913 where the specified schema was not supported.

Please make sure that the project that hosts the Reporting REST service is using the version that supports the required XML versioning. I recommend running the Upgrade Wizard in Visual Studio for easier upgrading to the required version. In case the issue persists, please send us the following information so we can review the additional details about your setup and provide you further suggestions:

1. Bin folder and the configuration file of the project that hosts the Reporting REST service so we can check the version of Telerik Reporting assemblies. 

2. The log with captured HTTP requests made during the time the problematic report is opened int the viewer.

3. The definitions of the master report and subreports so we can check the XML versioning."

 

Regards,
Katia
Progress Telerik