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.

Perhaps you can edit the sessionState line in the web.config file in the root 
of the CRM website to turn it on and add a timeout parameter (though this 
would be strictly unsupported, and you should test this in a non-production 
environment first, it might be worth a try):

    <sessionState timeout="60"  /> 

-- 
Matt Wittemann, CRM MVP
http://icu-mscrm.blogspot.com


"Drew" wrote:

> 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.
> 
>