This strongly suggests that your app is being recycled. Your session id will
be the same as long as your browser is kept opened. Have a look at your
application logs to find out what the w3c worker process is doing.
But then again, you've found a work around so why bother? Stateserver with a
loopback results in about a 10% performance hit. That's not a bad price to
pay to keep 1% of users happy.
--
Regards,
Alvin Bruney
Got tidbits? Get it here...
http://tinyurl.com/3he3b
"Karl Shifflett" <anonymous@discussions.microsoft.com> wrote in message
news:048201c3da11$a3f97640$a101280a@phx.gbl...[color=blue]
> Here is my web.config for the state server solution I
> provided.
>
> <sessionState
> mode="StateServer"
> stateConnectionString="tcpip=127.0.0.1:42424"
> sqlConnectionString="data
> source=127.0.0.1;Trusted_Connection=yes"
> cookieless="false"
> timeout="20"
> />
>
>[color=green]
> >-----Original Message-----
> >This is how I got around this.
> >
> >I changed the location of the session variables to
> >stateserver and just used the loopback address for the[/color]
> web[color=green]
> >server and fired up the stateserver on the web server and
> >have not had any problems since.
> >
> >[color=darkred]
> >>-----Original Message-----
> >>I have an intermittent problem that occurs on a very[/color]
> >small number of[color=darkred]
> >>browsers that access my website. The strange thing is[/color]
> >this: my site works[color=darkred]
> >>perfectly for 99.9% of browsers. The behavior described[/color]
> >below occurs for[color=darkred]
> >>0.1% of users, and so far I've only seen it on IE 6.0.
> >>
> >>My ASP.NET website is set up like this:
> >>
> >>1. Logon page - Collect username / password and verify[/color]
> >against the DB. If[color=darkred]
> >>OK, store the UserID in Session["UserID"] and redirect[/color][/color]
> to[color=green]
> >Main Page[color=darkred]
> >>
> >>2. Main page - If Session["UserID"] == null, redirect to[/color]
> >Logon page,[color=darkred]
> >>otherwise display the page. Includes hyperlink to Second[/color]
> >Page.[color=darkred]
> >>
> >>3. Second page - If Session["UserID"] == null, redirect[/color]
> >to Logon page,[color=darkred]
> >>otherwise display the page.
> >>
> >>Here is what happens in these very small number of[/color][/color]
> cases -[color=green]
> >- the user can[color=darkred]
> >>authenticate on the logon page successfully and gets[/color]
> >redirected to the Main[color=darkred]
> >>Page. However, upon clicking the link to go from the[/color][/color]
> Main[color=green]
> >Page to the Second[color=darkred]
> >>Page, the Session loses the variable and Second Page[/color]
> >redirects the user to[color=darkred]
> >>the Logon page.
> >>
> >>To debug this problem, I added a display of the[/color]
> >Session.SessionID + ":" +[color=darkred]
> >>Session["UserID"] variables at the bottom of the page.[/color]
> >Here are the results:[color=darkred]
> >>
> >>Logon page... vmhgea20gz4azp550f203omh:
> >>Main page... vmhgea20gz4azp550f203omh:24665
> >>Second page... vmhgea20gz4azp550f203omh:
> >>
> >>These results indicate that the SessionID is remaining[/color]
> >constant throughout[color=darkred]
> >>the test, but that the Server is somehow losing the[/color]
> >Session["UserID"][color=darkred]
> >>between the Main Page and Second Page. This would seem[/color][/color]
> to[color=green]
> >indicate that it[color=darkred]
> >>is a server issue, however, it only happens for 0.1% of[/color]
> >visitors and with[color=darkred]
> >>those particular visitors it is a constant repeatable[/color]
> >behavior. I have[color=darkred]
> >>instructed those users to delete their cached files and[/color]
> >cookies and reboot,[color=darkred]
> >>but it didn't help. The users have all the Windows[/color]
> >Updates in place.[color=darkred]
> >>
> >>Has anybody else seen this problem or know of its[/color]
> >solution?[color=darkred]
> >>
> >> Thanks!!
> >> Michael Carr
> >>
> >>
> >>.
> >>[/color]
> >.
> >[/color][/color]