Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Application pool web config issueApplication pool web config issue
Previous
 
Next
New Post
11/21/2009 7:22 PM
 

hello,

i'm using webhost4life for hosting my dnn portal.  users are logged out automatically after about twenty minutes of inactivity.  they told me that the application pool on the server is recycled every few minutes.  one of their techs included the following code into the web.config file:

    <sessionState mode="StateServer"
                      stateConnectionString="tcpip=127.0.0.1:42424"
                      cookieless="false"
                      timeout="300">
    </sessionState>

this has had no effect at all.  i told them this and they said that i would need to step up to the next plan which is almost $100 per month so that i would have full control of the application pool.  that is not going to happen any time soon.  i also tried setting how long users are allowed to be logged in in the host settings to larger number.  that had no effect either.  does anyone know of an effective code or utility that can be included in the root that will force the server to allow users to stay logged on for a period that i choose.  two or three hours would be sufficient :)

Thanks for the help guys :)

Brandon

 
New Post
11/22/2009 5:03 AM
 

DNN does not use sessions, i.e. session state settings are useless

log out is a cookie issue, are you sure, your users are logged out or just can't submit?

if you increase timeout of the persistent cookie in web.config from 0 to 10000 minutes, the users won't get logged out for this duration.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
12/4/2009 3:09 PM
 

users are definately logged out.  there is limited access to pages based on role.  when the user is automatically logged out, the private pages are not viewable.  i added the number 10000 to the persistent cookie in web.config.  that seems to have accomplished nothing.  do i need to take out the session state code?  is there a way to avoid the application pool reset so that users are not logged out?  does that even make sense?

there is also an issue with users having to log in twice.  when a user logs in he is automatically redirected to a page based on his role.  customers go to customers page, technicians go to technicians page, etc.  sometimes, not always, when a user logs in and is redirected to the page associated with his role; if he uses a link on that page which points to another page that is associated with his role, he is automatically logged out and must log in again.  in these cases, time has nothing to do with it.  i can log in, click a link all within 5 seconds, and i'm automatically logged out.  its a bug in dnn, i'm sure of it.  what can be done about any of this?  customers will have an awful experience if these problems don't get fixed.  ya know?

 
New Post
12/4/2009 6:45 PM
 

Sounds like there is more than one thing going on here... so we should track them down one at a time.  It is not likely a bug associated with normal use, or we'd be hearing a LOT about it...but having said that, you could have a unique combination of configuration that exposes a new bug... lets see if we can figure that out.

First thing is to establish that "session" (in the IIS or ASP.net sense) has nothing to do with DNN... DNN does not use it (due to security issues).  So those web.config settings have absolutely no effect on DNN at all.

The logging in twice problem is interesting... how are you handling the redirect by role?


Scott Willhite, Co-Founder DNN

"It is only with the heart that one can see rightly... what is essential is invisible to the eye. "
~ Antoine de Saint-Exupéry

 
New Post
12/5/2009 5:47 AM
 

please try to isolate the circumstances, under which users are logged out. There might be a link or a 3rd party module with an issue. Make sure to use relative paths only, e.g. if one link uses www.domain.com and the other one just domain.com, these are treated like separate domains. Unfortunately there is a bug in DNN, not mapping this properly. 

I suggest to remove the session state statement, except you are using 3rd party modules requiring sessions. 


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Application pool web config issueApplication pool web config issue


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out