Forms authentication failed for the request for ASP .NET 4 Web App...

Hi,
I'm having an issue in determining what might be causing an ASP, .Net4 web app developed in c# to stop working and display the stack trace page I've attached. I've reviewed the items in the stack trace and they seem to be a red herring. I reviewed the Event Viewer on the server and found that leading up to the eventual disruption of the web app many Informational entries with "Forms authentication failed for the request. Reason: The ticket supplied has expired" occured. The rest of the event viewer info is in the other attachment.

This just started happening the other night, and I even setup an alternate link from another web server, and the same thing occured. The one change has been in the usage of the system in that it has jumped from 5 simultaneous users to 25-30. After a couple hours without any intervention on my part it will begin working again. I've done a reboot of the server, but that did not help.

There are other web apps on the web server (non asp), and they are not impacted by this. In fact, the web server itself isn't fazed by the ASP app going down.

Any thoughts? I'm not familiar with "Forms authentication failed for the request. Reason: The ticket supplied has expired", and what it might suggest.

Cheers,
Ty
New-Text-Document--4-.txt
Error.jpg
MedtronicVascSRAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Daniel Van Der WerkenIndependent ConsultantCommented:
0
MedtronicVascSRAuthor Commented:
Thanks for the response. In reading about "slidingExpiration" it appears by default it is set to true, which is the suggestion in the recommended link:

Property Value
Type: System.Boolean
true if sliding expiration is enabled; otherwise, false. The default is true.
http://msdn.microsoft.com/en-us/library/system.web.security.formsauthentication.slidingexpiration.aspx

Have you experienced this before?

I'm going to read this article to better understand Form Authenication:
http://support.microsoft.com/kb/910443

Cheers,
Ty
0
Daniel Van Der WerkenIndependent ConsultantCommented:
Sorry. I've not experienced that exact issue. Some other stuff you could try is to track the Windows.Identity of the entity attempting to access the page via forms auth, etc. The articles you're reading should be able to point you as to more information about that. This is how I'd look into the issue.
0
Why Diversity in Tech Matters

Kesha Williams, certified professional and software developer, explores the imbalance of diversity in the world of technology -- especially when it comes to hiring women. She showcases ways she's making a difference through the Colors of STEM program.

CodecaesarCommented:
Hi

Have you checked your application pool settings?  Delete and recreate the pool and add your site to the newly created pool.

or

http://www.dotnetfunda.com/articles/article141.aspx
0
MedtronicVascSRAuthor Commented:
Hi,
Per your suggestion I re-created the application pool settings for the web app. I also bumped the 20 minute timeout to 60, but they experienced issue again during the night (they are using the web app in Ireland). The communication I received this morning from the project manager, and training coordinator may shed some light on the matter. In the email were instructions to the people being trained to the system, and they posted the url to the site. I quickly noticed the url, however, was not the oficial one that I'd sent out, but instead an url with a session id from when the training coordinator logged in. So instead of using
www.mydomain.com/app/etrs2/etrs2apps/ 

they were having people log in to the site with:
www.mydomain.com/app/etrs2/etrs2apps/(S(eqzgswqjufwm1nmadmchx2zr))/Default.aspx

I'm not sure, but wouldn't having 20+ people logging into the site with the same session id create some issues?

Cheers,
Ty
0
MedtronicVascSRAuthor Commented:
Hi,
I eventually tracked down the problem. The reason the error occured was due to an Oracle DB error that was being thrown when the limit of open cursors was exceeded. Easy enough fix for that!

Cheers,
Ty
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MedtronicVascSRAuthor Commented:
At the end of the day all the presenting errors, etc threw us off from the real issue.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
ASP.NET

From novice to tech pro — start learning today.