Print Preview Not Working for Single Page Report

4 posts, 0 answers
  1. Hesham Desouky
    Hesham Desouky avatar
    28 posts
    Member since:
    Oct 2012

    Posted 29 Oct 2015 Link to this post

    We are using Telerik Reporting 2015 Q2 using HTML5 MVC Viewer and REST Web API services.

    Everything working fine and the report rendered correctly and exports fine. Event the print functionality is working great.

    But when clicking the print preview button for single page report, it fails. From browser console we see that the request receives 400 response.

    The same print preview works when the rendered reports has 2 pages or more.

    We are using SQL Server Database for caching.

    Are we missing something?

  2. Stef
    Admin
    Stef avatar
    3047 posts

    Posted 29 Oct 2015 Link to this post

    Hello Hesham,

    Please test upgrading to the latest available Telerik Reporting Q3 2015 v9.2.15.930 and implement the ReportsControllerBase per the steps in the updated How To: Implement the ReportsController in an application.

    Then switch the Storage to use a proper IStorage implementation depending on how the application is deployed - REST Service Storage (you may need to use MsSqlServerStorage).


    I hope this information is helpful.

    Regards,
    Stef
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  3. DevCraft banner
  4. Hesham Desouky
    Hesham Desouky avatar
    28 posts
    Member since:
    Oct 2012

    Posted 29 Oct 2015 in reply to Stef Link to this post

    Hello Stef,

    Thanks for the reply. We already did all what you mentioned except the upgrade to latest version. Currently we are in Q2 2015.

    Is this fixed in Q3 2015?

  5. Stef
    Admin
    Stef avatar
    3047 posts

    Posted 30 Oct 2015 Link to this post

    Hello Hesham,

    Based on your screenshot there is a 404 error on getting a document from the server. The reasons for such error can vary from settings of the viewer, registered routes for the Reporting REST service or expired cache.
    Testing with the latest possible Telerik Reporting version can eliminate reason as expired cache, because in Q3 2015 we provided settings for controlling the cache timeout - Cache Management.

    If it is a matter of routing, using Fiddler you can record all requests sent from the viewer to the server and their responses content. Thus you can compare URLs and if they are formatted correctly.

    Regards,
    Stef
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
Back to Top