Forms authentication failed for the request. Reason: The ticket supplied has expired.

  • Thread starter Thread starter Gibble
  • Start date Start date
G

Gibble

Hi,

We have a javascript on a page that calls a .NET web service. Oddly,
in our web servers event logs the following errors kept repeating
every minute (that made sense since the web service was on a minute
timer).

Event code: 4005
Event message: Forms authentication failed for the request. Reason:
The ticket supplied has expired.
Event time: 5/11/2007 11:38:14 AM
Event time (UTC): 5/11/2007 4:38:14 PM
Event ID: 8d4cef6673914d6db1c5cc3c641cd67e
Event sequence: 18473
Event occurrence: 112
Event detail code: 50202

Application information:
Application domain: /LM/W3SVC/692275466/Root-1-128233734034204773
Trust level: Full
Application Virtual Path: /

Process information:
Process ID: 7716
Process name: w3wp.exe

Request information:
Request URL: http://domain:port/WebServices/service.asmx/service?userId=&lastMsg=671498
Request path: /WebServices/service.asmx/service
User host address: 82.81.177.24
User:
Is authenticated: False
Authentication Type:


When I try to recreate this error I can't, everything seems fine. I
looked at the IIS logs, and the IP that caused it hit a couple pages,
then this web service every minute. So the user was idle.

The part that's baffling me is why this error happened, and ONLY for
one user...?

Any ideas would be appreciated.

Thanks.
Chad
 
This is very odd. Several IPs have been generating this error in our
event logs. But oddly, not enough that it indicates an error in our
code. Only a person or two will be generating this error at a time,
meanwhile 100s are logged into the site at any given time (plus
anonymous users).

I'm pulling out my hair here...

-C
 
Hi, how are you trying to reproduce the error? It's not clear whether you
meant the user is idle or not. One reason for the error could be the user was
idle for a long time in which case it timeout and logged it as an error. If
this is so, then no need to worry about it.

HTH
 
I can't recreate it...as I don't yet know what's causing it exactly.

I've done some research and some people seem to think it's because the
session timeout is longer than the forms authentication cookie
timeout, but I'm not using sessions:

<authentication mode="Forms">
<forms loginUrl="login.aspx" name=".FOO" protection="All"
path="/" timeout="120" cookieless="UseCookies" />
</authentication>

<sessionState mode="Off"/>

So I don't know what's causing this...?
 
Any ideas?

I can't recreate it...as I don't yet know what's causing it exactly.

I've done some research and some people seem to think it's because the
session timeout is longer than the forms authentication cookie
timeout, but I'm not using sessions:

<authentication mode="Forms">
<forms loginUrl="login.aspx" name=".FOO" protection="All"
path="/" timeout="120" cookieless="UseCookies" />
</authentication>

<sessionState mode="Off"/>

So I don't know what's causing this...?
Click to expand...
 
try using slidingExpiration="true" in the forms tag & also make sure forms
timeout is same as session timeout.
 
Back
Top