JeffP@Work
9/26/2006 12:44:00 AM
I'm sorry if this post precludes any valid responses, however I've had
similar issues with either using javascript Back()-1, or the browser back
button...
So I script my own back buttons that I run into an overloaded method for any
similar controls.
I use this by setting the commandArg and Text as needed on any previous
post, I keep them in Nav panels.
Anyway it functions for the current datagrid (I know... badthing) to step
back thru the recordset or to actually go back to a previous page.
I get most if not all of what I need to know from the cmdArg.
Painful as it is to do, it enables me to have more control and less suspects
as to why it's not working.
HTH
JeffP....
"jhagerty" <jhagerty@etechsolutions.com> wrote in message
news:eBT4p5syGHA.4336@TK2MSFTNGP06.phx.gbl...
> Hi all, I have an asp.net 1.1 web app that uses mobile controls and forms
> authentication. I recently added a "remember me" functionality, allowing
> the
> user to stay logged into the site between browser sessions (the login page
> makes use of the RedirectFromLoginPage method).
>
> In doing so, I am getting an intermittent error:
>
> "The page requires session state that is no longer available. Either the
> session has expired, the client did not send a valid session cookie, or
> the
> session state history size is too small. Try increasing the history size
> or
> session expiry limit."
>
> This happens when a user tries to re-submit a form that has data driven
> drop
> down boxes. The weird thing is, the form works on the first pass; but, if
> the user drills down into the site, then uses the "Back" button to get
> back
> to the form, they get the error. They can bypass it by clicking the link
> to
> bring up the form, which then re-populates all the drop down boxes.
>
> I have a sense that this is something simple, but have no idea what it
> might
> be. Any help is appreciated, thanks.
>
>
>