This is a migrated thread and some comments may be shown as answers.

Reporting InvalidClientException

3 Answers 319 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
NerdBrick
Top achievements
Rank 1
NerdBrick asked on 22 Jul 2015, 09:32 PM

Hello, 

We are using Telerik Reporting in a WebApp that is open all day in a browser for the users as they do their work. The Reports are Ajax reloaded in the same report view on demand, but if the reporting is not touched for longer than an hour we get an exception from Telerik. If they refresh the page, it will work fine again, however they will loose the work they are doing. How can we hold a report view open for a longer period of time? 

 

{"message":"","exceptionMessage":"Client with ID '092435-2fa6' not found. Expired.","exceptionType":"Telerik.Reporting.Services.Engine.InvalidClientException","stackTrace":" at Telerik.Reporting.Services.Engine.ReportEngine.WithClient[T](String clientID, Func`2 func)\r\n at Telerik.Reporting.Services.WebApi.ReportsControllerBase.CreateInstance(String clientID, ClientReportSource reportSource)\

 

Is there is a Cache setting we need to change to improve this time out?

Thank you. 

3 Answers, 1 is accepted

Sort by
0
Stef
Telerik team
answered on 27 Jul 2015, 08:41 AM
Hi,

Based on the error message, you are using the Reporting REST service. to control the cache timeout you can work with the service's ReportServiceconfiguration (introduced as of v9.0.15.422). For more details, please check HTML5 Report Viewer and Reporting REST services.

I hope the provided 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
0
NerdBrick
Top achievements
Rank 1
answered on 27 Jul 2015, 04:34 PM

Thank you for your timely reply. This will be great information to have​ as we are have a scheduled task to update and test this version of Telerik Reporting coming up. We are still running Q1 2014. Sorry I can report back just yet if this fixed the problem, but hopefully after we upgrade we can check this out. 

 

0
Stef
Telerik team
answered on 28 Jul 2015, 09:27 AM
Hi,

You can test if the settings produce the desired result with the local demos installed by default under C:\Program Files (x86)\Telerik\Reporting Q2 2015\Examples.

We plan to provide one more setting that will invalidate the cache even if the same report is requested with the same set of parameters values, until this setting is available the approach to achieve this is to submit unique set of parameters (use custom UI and submit a new Date() to a DateTime report parameter in the report).

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
Tags
General Discussions
Asked by
NerdBrick
Top achievements
Rank 1
Answers by
Stef
Telerik team
NerdBrick
Top achievements
Rank 1
Share this question
or