In general, when a report is requested, the document is processed and rendered on the server in HTML format for the viewer. The document's pages(HTML) and resources(images) are cached in the location specified by the Reporting REST service's Storage, which are stored for the given client(viewer ID).
The cached files can be missing if the client's session expires and another request to the Reporting REST service makes a clean in the cache storage - Cache Management: HTML5 Report Viewer and Reporting REST services
Having the above into account, please test to set the ClientSessionTimeout
of the service to a value greater than zero and check if the error occurs again. Also verify the custom report resolver returns the same report definition on each call, while a report is being resolved (there are several calls to the service's resolver). Note that only the initially requested report is handled in the custom resolver's Resolve method. NavigateToReport.ReportSource
property is resolved internally.
Test also to switch to the MsSqlServerStorage IStorage implementation
In order to investigate the problem further, please open a support ticket and send us a demo project that reproduces the problem.
Thank you for your cooperation.
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?
Telerik Feedback Portal
and vote to affect the priority of the items