I'm rather new to Telerik and I'm picking up an ASP.NET MVC project at work from a previous developer...so bear with me.
I recently updated from 2016 R3 version 10.2.16.1025 to 2019 R2 version 13.1.19.618 and mistakenly used the updating tool for non web projects from the Upgrade Wizard for Visual Studio Telerik Reporting. I manually updated the reference dll's and checked all of the required references but the report viewer does not render correctly. The behavior is shown in both Chrome and Firefox. When the report initially loads everything is collapsed into the top left corner. If something resizes the page or refreshes the page it corrects itself. Please see attached images. Is there anymore information needed to help troubleshoot?
Thank you
7 Answers, 1 is accepted
Firstly you can check if there are any errors through the dev tools of the browser. If there are any, send us screenshots which demonstrate the issues. We also need to know if there are some custom styles which might cause errors.
I see that the Font Awesome template is used. You can try to remove it and use the default template to see if the issue will be reproduced again.
You can also try using the Upgrade Wizard which will upgrade the references to the assemblies of the new version, the configuration file, as well as the web page/user control files (aspx/ascx) with references to the Telerik Reporting assemblies.
If the issue is not resolved, consider opening a Support ticket where you can send us the project. We will need all styles, as well as the plugins if such are included.
Regards,
Neli
Progress Telerik
Rank 1
Hello Neli, thank you for your reply.
I checked the dev console in both Chrome and Firefox and I do not see any errors that show up. The only error I see is when I use Fiddler. I receive a 404 error on this file /ReportViewer/js/kendo.custom.min.js.map. I should mention that I'm using the template and the dll's straight from the installer with no modifications.
I've done a little tweaking and I got the report to render correctly...it's just missing the parameters area. The parameters area defaults as hidden when the report loads.Even if I set .ParametersAreaVisible(true) it pretty much ignores it.
I changed to using the default template and the report is sized to the initial_load picture above. Using the Font Awesome template it renders correctly but the parameters area is hidden. I checked my site.less file for the styles and the height of the report viewer is set to 700px but it's completely ignoring it for some reason. Maybe it has something to do with that style file?
Also, previously in the 2016 release there was a kendo.subset.2015.3.390.min.js file but moving to 2019 that subset file doesn't exist. Instead I read that I have to replace it with a file like kendo.all.min.js; stated here https://docs.telerik.com/reporting/html5-report-viewer-system-requirements#important-settings. However I'm not sure where that file exists.
I used the upgrade wizard at the beginning and had a many more problems because I didn't realize it didn't update the references (this is a web MVC project). I updated the dll's to the correct ones and all of the references but the reports still do not load correctly. I used the instructions listed here https://docs.telerik.com/reporting/telerik-reporting-rest-host-http-service-using-web-hosting#manually-configuring-telerik-reporting-rest-service-on-iis.
https://www.telerik.com/forums/report-viewer-is-to-small-in-some-browsers
This is very similar to my issue when I use the default template but I'm not sure where this person updated the information.
I believe that's all of the updated information I've found. The only thing I can assume is it's a style issue but I'm not sure where.
The Kendo UI is not required if you are only going to use the widgets for the needs of HTML5 Report Viewer. Telerik Reporting provides a JS file containing a subset of the used by default Kendo UI widgets. With our latest versions this subset is delivered by the REST Service, hence it is not necessary to refer it in the page.
We have not experienced the described problem with missing parameters area so far. We would need a sample project for investigation. You still have the possibility to open a Support ticket where you can send us the project.
Regards,
Neli
Progress Telerik
Rank 1
Neli,
What would be the best course of action to upgrade between 2016 R3 and the current 2019? After the 2017 release there were numerous breaking changes (compared to 2016) such as method name changes and the kendo being used in a different way. Simply changing the dll references and js/css files does not seem to work.
Braden
Indeed, for upgrading reporting project it is not enough to switch the references. In the case of breaking changes our Upgrade Wizard will modify also the code of the reports.
You can take a look at How to Upgrade an old project to the latest Telerik Reporting version KB article for instructions on upgrading older projects.
Another option is to use the Upgrade Wizard directly to the newest version, and update the NuGet packages one by one manually.
Regards,
Neli
Progress Telerik
Rank 1
Neli,
I thought the Upgrade Wizard didn't support web projects? My project is an ASP.NET MVC 5 application.
Braden
When it comes to web applications, the Upgrade Wizard can be used. Web Site projects are not supported because Web Sites assembly references are handled differently.
Regards,
Neli
Progress Telerik