Asp.net Forms Authentication Error
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site forms authentication failed for the request. reason the ticket supplied has expired. iis 7 About Us Learn more about Stack Overflow the company Business Learn more about
Event Code: 4005
hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join event detail code: 50202 the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up ASP.NET Forms Authentication failed
Event Id 1315 Event Code 4005
for the request. Reason: The ticket supplied has expired up vote 14 down vote favorite 2 I am getting this error many times in the event log and users are logged out. Event code: 4005 Event message: Forms authentication failed for the request. Reason: The ticket supplied has expired. Event time: 3/10/2011 3:35:22 PM Event time (UTC): 3/10/2011 8:35:22 PM Event ID: fc2f70cc85014b0ca7dbb01471617b66 Event sequence: 3392 event detail code: 50201 Event occurrence: 1 Event detail code: 50202 Thoughts: I am not using web forms. I do not think the app pool is recycling. I compared the Process ID in several events and it is equal. My machine key is not AutoGenerate. asp.net .net authentication forms-authentication share|improve this question edited Dec 12 '15 at 14:38 Zanon 3,95082946 asked Mar 10 '11 at 22:16 Amr 81113 Unless someone at Stack Overflow has developed ESP, you should probably explain which software you are using, and probably which OS. It might also help to phrase your question in the form of a question. –pjmorse Mar 10 '11 at 22:20 1 i recognize the babble as asp.net and have fixed the tags. –x0n Mar 10 '11 at 22:22 did you ever find a solution to this one? –AMember Oct 10 '13 at 15:56 1 Related questions: Forms authentication failed for the request. Reason: The ticket supplied has expired and Error 4005 Forms authentication failed - ticket supplied has expired –Owen Blacker Mar 10 '14 at 11:49 did you tried any solution? –Kiquenet Jul 21 at 15:18 add a comment| 4 Answer
FerrandezSeptember 16, 200910 0 0 0 I recently had a customer that just moved from Windows 2008 to Windows 2008 R2 (changing from IIS 7 to IIS 7.5) and after the move they got some weird
Asp.net Forms Authentication Not Working
forms authentication errors in the event log The problem They have two applications (MyWebApp and
Membership Credential Verification Failed
MyLoginWebApp) where forms authentication is dealt with in MyLoginWebApp
One games Xbox 360 games PC https://support.microsoft.com/en-us/kb/910439 games Windows games Windows phone games Entertainment All Entertainment Movies & TV Music Business & Education Business Students & http://www.hanselman.com/blog/WeirdTimeoutsWithCustomASPNETFormsAuthentication.aspx educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security forms authentication Internet Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Band Microsoft asp.net forms authentication Lumia All Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
day to day, it always seems to come down to debugging weird stuff. So, here's something weird that happened today (actually it's been happening over the last week in QA). Someone logs into an ASP.NET application successfully and does some stuff. They wait for 10.5 minutes. That means no clicking, just waiting. Then they click and get the next page successfully. Then the click on the NEXT (the second since they've been waiting) and get kicked out to the login page. Since our FormsAuthentication stuff not only authorizes the user into ASP.NET but also carries with it tokens into other "session-like" systems, folks dug around in those systems initially looking at Audit data, logs, everything. It just doesn't make sense. The FormsAuthentication timeout is set to 20 minutes and folks are getting "logged out" at 10.5 minutes. They set the timeout to 600 minutes and folks get kicked at 10.5 minutes. Is the timeout value being ignored? As with most things, we return to first principles and pull out ieHttpHeaders. Why? Because in the context of a Web Application, clicking and looking at HTML only tells you that you clicked and look at some HTML. TIP: When using ieHttpHeaders or any sniffers, turn OFF Images in your browser. Chances are they aren't the issue (although they might well be) but initially you'll save yourself some clutter in initial debugging.) So, here's what we saw (abridged and #commented): #LOGGING INPOST /fooapp/Login.aspx HTTP/1.1Content-Type: application/x-www-form-urlencodedAccept-Encoding: gzip, deflateUser-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)Host: foo.corillian.netContent-Length: 104FI=fooapp&Destination=Accounts%2Ffooapp%2Fsummary.aspx&UserName=BAR #LOGIN COOL, REDIRECTING and setting NEW AUTH COOKIEHTTP/1.1 302 FoundDate: Mon, 11 Jul 2005 18:54:31 GMTServer: Microsoft-IIS/6.0Location: http://foo.corillian.net/fooapp/somepath.aspxSet-Cookie: Authe