Last post Jul 16, 2007 10:05 PM by Zhao Ji Ma - MSFT
Jun 29, 2007 12:40 PM|Jorel|LINK
I get the "Page requires session state that is no longer available. Either the session has expired, ....." error when I use
but i can use a page just find that just inherits UI.Page.
I've tried setting cookieless=true...setting the historySize greater, and increasing the timeout, nothing works!. I'm using a blackberry to access the page.
Like I said, It's not an issue with a regular page...i can post back and retain info just fine.....but i want to take advantage of the mobile controls....What gives????
Jul 04, 2007 01:31 AM|Zhao Ji Ma - MSFT|LINK
Have you checked the IIS Log? The cookieless session is using token string in the URL to indicate its session. e.g.
The existence of (p5bbz555jx3f34552km4bn55) indicates that cookieless sessions are enabled for this application. So I think if you look for the last occurrence of the string token before the problem occurred, the log entries around the time may contains
information telling what had happened.
Jul 05, 2007 10:58 AM|Jorel|LINK
Yeah, I couldn't find any error in the log file when cookieless sessions are enabled? Like I said, the page never opens up initaially, just trys to redirect 7 or 8 times and then comes back with a max number of redirects reached.
How come a regular ui.page works fine (viewstate and session), but a ui.mobilepage bombs out?
I need more of an explaination of mobilepage, because any tutorial or example i follow will not work.
Jul 08, 2007 04:45 AM|kamrul3d|LINK
as far i know session state is not present in wap.
Jul 12, 2007 12:26 PM|grimms1|LINK
Check iis application pool for that application to assure that the recycle worker process is set to default. The default is unchecked for everything on the "recycle" page.
Also on the Identity tab, the security account is usually "network service".
Jul 13, 2007 04:46 AM|MikeLim|LINK
Try setting SessionState to StateServer e.g.
Remember to start ASP.NET State Service from Services MMC.
Jul 16, 2007 10:05 PM|Zhao Ji Ma - MSFT|LINK
Do you use a tilde ("~") in a path?
For mobile pages, if your application relies on cookieless sessions, or might receive requests from mobile devices that require cookieless sessions, using a tilde ("~") in a path can result in inadvertently creating a new session and potentially losing session
data. To set a property on a mobile control with a path such as "~/path", resolve the path using
ResolveUrl "~/path" before assigning it to the property.