Hello,
We are using Reports.Web Ultimate 2015.3
When user opens mobile (HTML5) editor and after about a minute of inactivity he gets an error saying "Session on the Server is Complete!"
Our ASP.NET application session is set to 120 minutes. How do we extend editor session to not receive this error message?
Thanks!
Mobile designer error "Session on the Server is Complete!"
Re: Mobile designer error "Session on the Server is Complet
Hello.
This message is shown if it was impossible to get a report from server cache. By default the cache mode is set to Page.
It seems that your server clear its cache.
Please, try to change the CacheMode proeprty to the StiCacheMode.Session.
Thank you.
This message is shown if it was impossible to get a report from server cache. By default the cache mode is set to Page.
It seems that your server clear its cache.
Please, try to change the CacheMode proeprty to the StiCacheMode.Session.
Thank you.
Re: Mobile designer error "Session on the Server is Complet
Hey,
I am having a similar problem with the StiMvcMobileDesigner. With the StiDesignerCacheMode set to Page I get the "Session on the Server is Complete" error, but when I change the StiDesignerCacheMode to Session I get an error that the StiReport is not Serializable. How do I get the report desginer to work with caching the report in the session?
Thanks
I am having a similar problem with the StiMvcMobileDesigner. With the StiDesignerCacheMode set to Page I get the "Session on the Server is Complete" error, but when I change the StiDesignerCacheMode to Session I get an error that the StiReport is not Serializable. How do I get the report desginer to work with caching the report in the session?
Thanks
Re: Mobile designer error "Session on the Server is Complet
Hello,
We have made some improvements and checks in that direction. Please try to check the last build.
If the issue still present, please send us a simple project which reproduces the issue for analysis.
Thank you.
We have made some improvements and checks in that direction. Please try to check the last build.
If the issue still present, please send us a simple project which reproduces the issue for analysis.
Thank you.