• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 676
  • Last Modified:

Session timeouts using forms authentication

We have a customer using CRM in a hosted environment, setup to use forms authentication.  They want their login to remain valid for one hour, but it currently times out right around 20 minutes.  We've set everything we can find in terms of timeouts, but nothing has changed this.  So far, this is what we have configured for timeouts:

* Website in IIS
**Connection timeout: 3600 seconds, HTTP Keep-alives enabled
**Running under ASP.NET 2.0.50727
**ASP.NET configuration: State Management: Session timeout set to 60 minutes (for main site, and Reports & ReportServer under Locations)
**Global ASP.NET configuration: State management: Session timeout set to 60 minutes

*CRMAppPool in IIS
**Recycle worker processes: 1740 minutes
**Shutdown worker processes after being idle: 1500 minutes

The cookie that users get when logging in is set to expire at the end of their session, so it doesn't seem to be a cookie expiration issue.  We've looked through CRM and haven't found anything relating to timeouts.  Any help is appreciated.
0
up2speed
Asked:
up2speed
  • 2
1 Solution
 
rama_krishna580Commented:
Hi,

The session Timeout is a sliding expiration time, meaning whatever your page access session state, the expiration time will be moved forward. Note that as long as a page has NOT disabled session state, it will access the session automatically when requested.

One of the things that causes the session to expire is if the bin folder of the project is opened. So first please make sure that doesent happen. Also if the project solution on the server is build even that breaks the session.

Also you can check out these links:
http://forums.devx.com/showthread.php?threadid=99428
http://www.dotnetspider.com/Technology/QA/ViewQuestion.aspx?QuestionId=17
http://www.experts-exchange.com/Programming/Programming_Languages/Dot_Net/ASP_DOT_NET/Q_21084438.html

R.K
0
 
up2speedAuthor Commented:
Thanks for the reply.  Unfortunately, it doesn't help.  This is a 3rd party application, not something I wrote.  I don't need info on accessing the session state in an application; I need info on fixing MS CRM's buggy session state timeouts.  As I stated above, all session timeouts have been changed to 60 minutes, but it still times out after 20.
0
 
up2speedAuthor Commented:
We've figured this problem out.  The setting is actually stored in the registry on the web server.  The key is HKLM\Software\Microsoft\MSCRM\SessionExpirationMinutes, and is the number of minutes the session can be inactive before it expires.  There is also a list of other registry settings at http://msdn2.microsoft.com/en-us/library/aa683650.aspx
0
 
DarthModCommented:
PAQd, 500 points refunded.

DarthMod
CS Moderator
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now