[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

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

Posted on 2012-03-30
7
Medium Priority
?
1,029 Views
Last Modified: 2012-06-21
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
0
Comment
Question by:MedtronicVascSR
  • 4
  • 2
7 Comments
 
LVL 20

Expert Comment

by:Daniel Van Der Werken
ID: 37789641
0
 

Author Comment

by:MedtronicVascSR
ID: 37789813
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
 
LVL 20

Expert Comment

by:Daniel Van Der Werken
ID: 37791769
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
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 2

Expert Comment

by:Codecaesar
ID: 37792814
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
 

Author Comment

by:MedtronicVascSR
ID: 37797334
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
 

Accepted Solution

by:
MedtronicVascSR earned 0 total points
ID: 37857259
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
 

Author Closing Comment

by:MedtronicVascSR
ID: 37877353
At the end of the day all the presenting errors, etc threw us off from the real issue.
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

ASP.Net to Oracle Connectivity Recently I had to develop an ASP.NET application connecting to an Oracle database.As I am doing it first time ,I had to solve several problems. This article will help to such developers  to develop an ASP.NET client…
IntroductionWhile developing web applications, a single page might contain many regions and each region might contain many number of controls with the capability to perform  postback. Many times you might need to perform some action on an ASP.NET po…
Screencast - Getting to Know the Pipeline
Is your OST file inaccessible, Need to transfer OST file from one computer to another? Want to convert OST file to PST? If the answer to any of the above question is yes, then look no further. With the help of Stellar OST to PST Converter, you can e…
Suggested Courses

873 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question