Instance id is expired when using f5

2 posts, 0 answers
  1. Professional
    Professional avatar
    1 posts
    Member since:
    Jan 2018

    Posted 07 Aug 2018 Link to this post

    Hi All ,

    we have two web servers, with f5 to manage the calls between these two web servers. so we call the web servers through f5 as round robin way. The telerick reporting generate an instance id for each session and under each session there are many clients, and the instance ID generated for the first call in the session. so If the instance ID created in the web server 1. so if the requests directed to web server 2 it returns an error the instance id is expired but if the requests directed to web server 1 it works.  so we need to make the instance ID is shared between the two web servers.

    I change the Telerik instance timeout configuration to be an hour instead of 15 minutes. also I make the cashing is File and make an shared folder for both servers. but still we have the same issue.


    Can Any one help  me to fix issue

  2. Silviya
    Silviya avatar
    440 posts

    Posted 10 Aug 2018 Link to this post


    I would post my answer from your support ticket that is opened on the same topic:

    "The issue might be connected to permissions, but we cannot be certain given the provided information. Thus, we suggest to try the following:

    By default, the REST Service uses File Storage which is suitable for single instance deployment and requires that you give full permissions to the applicable user for the folder where the storage is saved. You can test changing the File Cache to a different storage type, or change the folder where the file cache is stored to point to your shared folder. For more information, please check - IStorage implementation suitable for deploying in Web Farms where are listed the available storages with multiple instances support. Also the following articles might help too:
    How To: Configure MS Sql database storage
    How to: Use Redis storage 

    In case the issue persists, please try to debug the application and check for any exceptions or event viewer errors. You can also send us a runnable sample project which we can use to reproduce the issue and investigate further."

    Progress 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