Help Desk and PC Inventory Software by Gritware   Gritware Support Forums
Gritware Support Forums
Sign up Latest Topics
 
 
 


Note: This topic is locked. No new replies will be accepted.


Reply
  Author   Comment  
jwaller

Member
Registered:
Posts: 3
Reply with quote  #1 
A few times a day I will receive an error pop-up that states "Response.Redirect cannot be called in a Page callback."
This seems to happen at random, some days more often than others. When it does I have to refresh the page, it kicks me back to the login screen and I have to login again.
A lot of the time this seems to occur while webtracks is sitting idle, but sometimes within a minute or two of using webtracks, thus almost acting as an idle timeout to keep people from staying logged in indefinitely.
thoese

Moderator
Registered:
Posts: 491
Reply with quote  #2 
Hi,

This is due to the idle time-out timer. It works based off of the session state length (settable in Admin-Application Settings). When the timer expires the user is redirected to the sign-in screen.

This can happen when more than one browser screen is open and one of the screens timeout. The other one which didn't timeout then needs to have the user sign in again.

To minimize this behavior do the following...

1. Increase the session timeout length in Admin--Application Settings to 1000.

2. Open IIS, Expand the computer and click on 'Application Pools'

3. Right click on 'DefaultAppPool' and choose 'Advanced Settings'

4. Increase the 'Idle Time-out' value to 1000.

I will look into this and see if this can be handled more gracefully in a future version so you don't receive the error message you noted.

Thanks,

__________________
Todd @ Gritware
Other resources
Gritware.com
Knowledge Base
Web Tracks Help
jwaller

Member
Registered:
Posts: 3
Reply with quote  #3 
Thank you very much. I've made the suggested changes and will report any further issues.
thoese

Moderator
Registered:
Posts: 491
Reply with quote  #4 
Fixed...

In version 8.11 and newer session length has been moved out of the Web Tracks setting and is handled by IIS.  In version 9.00 and newer the app pool timeout has been increased.  These changes have reduced instances where these values come out of sync and cause this type of problem.

__________________
Todd @ Gritware
Other resources
Gritware.com
Knowledge Base
Web Tracks Help
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.