IIS 6.0 and session variables

[avantgd]

We support an ASP application that uses session variables.

After 8 months of working fine, the application has stopped working. After we log in, go to an edit page and click "Submit", the user is returned to the home page because a seesion variable is empty. The server shows the session.timeout is set to 20 minutes.

THe web host is telling us that "For some sites in IIS6, global.asa's do more damage than good. IIS will read them multiple times when session objects are defined (

http://support.microsoft.com/?kbid=172864),

and this basically stops on the existing session data (and causes databases to become locked and unedited by subsequent servers)".

This make no sense to us. We are not having trouble updating the database because we can never get that far. Has anyone else run into this problem?

 

[Sheco]

My guess is that the server guy did something to increase your "security" and that he doesn't really understand what he's done.

You can set and read Session and Application variables that are not defined in the global.asa. Perhaps make a pair of test pages. The first page sets one each of Session and Application variables. The second page reads and displaysthe values. Make them separate pages rather than a single page that does everything.

 

[Sheco]

Also that KB article is about IIS 3 running on Win NT4... fixed in 1997.