Ah, would this be caused by the session timeout being longer than the cookie
timeout ?
"Juan T. Llibre" <no***********@nowhere.comwrote in message
news:eY*************@TK2MSFTNGP06.phx.gbl...
| Does this happen after 25 minutes have elapsed ( the timeout you set ) ?
| Or, does it happen before the timeout has occurred ?
|
| Also, note that, to prevent compromised performance, and to avoid multiple
browser
| warnings for users who have cookie warnings turned on, the cookie should
be updated
| when more than half of the specified timeout has elapsed.
|
| This might cause a loss of precision...or that feature might be
non-functional.
|
|
|
|
| Juan T. Llibre, asp.net MVP
| asp.net faq :
http://asp.net.do/faq/
| foros de asp.net, en español :
http://asp.net.do/foros/
| ===================================
| "Adrian Parker" <ap******@nospam.nospamwrote in message
| news:ei**************@TK2MSFTNGP02.phx.gbl...
| We have an application that's running ok on most of our customers
machines,
| but on one of them we get an error. They're running on windows 2003
server
| with iis6. In the web.config, the authentication is set to forms, and
the
| form tag contains: timeout="25" slidingExpiration="true"
| >
| Event Type: Information
| Event Source: ASP.NET 2.0.50727.0
| Event Category: Web Event
| Event code: 4005
| Event message: Forms authentication failed for the request. Reason: The
| ticket supplied has expired. Event detail code: 50202
| >
| Any ideas ?
| --
| Adrian Parker
| Ingenuity At Work Ltd
|
|