Authentication Ticket Timeout



Our Forms authentication ticket is timing out much faster than it is suppose
I am auditing the application pool and the application is not restarting.
I am not using session cookies.
The timeout is set to 180 we are seeing lots of timeouts in under an hour.

<forms name="HR-xxx" domain="localhost"
loginUrl="http://localhost/HRxxx/LogIn.aspx" protection="All" path="/"
timeout="180" slidingExpiration="true" requireSSL="false">

<machineKey validationKey="1243...." decryptionKey="48..."
validation="SHA1" decryption="AES"/>

<sessionState mode="Off"/>

<add name="Application Lifetime Events Default" eventName="Application
Lifetime Events"
provider="EventLogProvider" profile="Default" minInstances="1"
maxLimit="Infinite" minInterval="00:01:00" custom="" />

Event Type: Information
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1315
Date: 8/6/2009
Time: 3:58:33 PM
User: N/A
Computer: HRINT
Event code: 4005
Event message: Forms authentication failed for the request. Reason: The
ticket supplied has expired.
Event time: 8/6/2009 3:58:33 PM
Event time (UTC): 8/6/2009 9:58:33 PM
Event ID: f27b4e1fc715401facc032ebb51a8d42
Event sequence: 47290
Event occurrence: 40252
Event detail code: 50202

Application information:
Application domain: /LM/W3SVC/1/Root/Perform-1-128940241439307777
Trust level: Full
Application Virtual Path: /Perform
Application Path: E:\Inetsrv\wwwroot\Perform\
Machine name: HR...

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

Request information:
Request URL: http://hr....
Request path: /Perform/Default.aspx
User host address: 128.1....
Is authenticated: False
Authentication Type:

Name to authenticate:

Custom event details:

For more information, see Help and Support Center at

Allen Chen [MSFT]

Our Forms authentication ticket is timing out much faster than it is suppose

1. Are you running Web Farm? If the machinekey on the server machines are
different it's possible to see this issue on a machine when it receives a
ticket that is generated by another machine.

2. Are you getting these logs when using one client to test? If not, it's
possbile that your clients send expired tickets.

To troubleshoot this issue you can add an HttpModule to log more
information about the submited ticket. You can refer to the following kb
article for more details:

In this way we can diagnose if the ticket is really expired or there're
other factors that cause this problem.

Allen Chen
Microsoft Online Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the

support we provide to you. Please feel free to let my manager know what you
think of the level of service provided.

You can send feedback directly to my manager at: (e-mail address removed).

Get notification to my posts through email? Please refer to


Note: MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community

or a Microsoft Support Engineer within 2 business day is acceptable. Please
note that each follow up response may

take approximately 2 business days as the support professional working with
you may need further investigation to

reach the most efficient resolution. The offering is not appropriate for
situations that require urgent, real-time

or phone-based interactions. Issues of this nature are best handled working
with a dedicated Microsoft Support

Engineer by contacting Microsoft Customer Support Services (CSS) at

This posting is provided "AS IS" with no warranties, and confers no rights.


How will logging help?
What we have done is login with 180 min expiration.
Verify values in ticket
Wait 40 minutes hit the site again, get redirected to login page.

bruce barker

you should run fiddler to see if the browser is sending the cookie
correctly. your proxy server may also be playing with cookies. also
check that the domain name does not change with redirects.

-- bruce (

Allen Chen [MSFT]

How will logging help?

Please see the following instruction in the kb

Log the values. I would recommend logging the following in addition to the
forms information. This will help you line up your forms authentication
information to the IIS logs, if necessary:

Date: Allows you to see when the request came in.
RequestType: Shows whether the request is a Get or a Post.
URL: Shows the pattern of requests leading up to the problem.
ClientIP: Ties in the requests to a specific client.

The above information can help to see when the request is received, who
sends it, etc. In addition, the log module logs the cookie information so
you can check the issue date and expire date of the submitted cookie. By
comparing to the request received time you can know whether the cookie is
really expired or maybe other factors cause this behavior.

Because there're several posibilities, I suggest you use the log module to
log these information first. Then we can see if we can get something from
the log.

Please let me know what you find from the log. For test purpose you can set
the timeout a little shorter, for example 2 minutes (if it can repro this

Allen Chen
Microsoft Online Support

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Latest member

Latest Threads