The INFO request is sent by the viewer to check the status of the report that is processed and rendered on the server - check Cache Management
. It can go to infinity or until the server returns an error in response.
from your screenshot indicates that the client id (the registered id of the viewer) cannot be found in the cache storage. Possible reasons:
- The Cache storage is not accessible.
Set an unique HostAppId for the Reporting REST service (Reportscontroller.cs).
Reconfigure the Storage property to use the second overload of FileStorage and specify a cache storage folder accessible by the application, preferably not the Reports folder, but a dedicated for cache one. In a web farm or with load balancing, you will need an MsSqlServerStorage.
Assure the IIS process (Application pool's identity) has read/write access to the configured cache storage.
About "An exception has occurred while processing 'table1' item:
System.Data.SqlClient.SqlException (0x80131904): Conversion failed when converting date and/or time from character string.
", check the report settings in a Report Designer. There must be a DateTime parameter or field. Verify you are passing a valid Datetime object, not a string as strings will be converted based on the server machine's culture to Datetime (possible source of conversion problems). Avoid passing an empty string as a value to report parameters - you can set default values to report parameters on designing the report.
Just in case it is a message formatting problem, update JSON.NET Nuget package to the latest available via VS Nuget Package Manager.
About "An error has occurred while rendering the report: System.Threading.ThreadAbortException: Thread was being aborted.
at Microsoft.Win32.Win32Native.CreateDirectory(String path, SECURITY_ATTRIBUTES lpSecurityAttributes)
", this is related to read/write access to the cache storage. The previously suggested settings of the Reporting REST Service Storage should affect this error.
The rest errors are related to the processing and rendering of reports. The errors point to bookmark and style settings. If you are modifying reports in code, please check - Changes on items in report events are not applied.
We will have to review the reports definitions to investigate further these problems.
Telerik by Progress
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