1

On my Windows 2008 R2 servers, every uncaught ASP.NET exception generates an event that shows in the Windows Application Eventlog.

On my Windows 2012 servers, none of them do.

Is there anything I can do, purely in configuration (not adding code to my application), to make my Windows 2012 servers show these exceptions?

EDIT: To clarify, my app does not write to the eventlog from code. The problem is that I expect when an app crashes, IIS will write to the eventlog. That's not happening.

The problem still exists to this day. I cannot depend on IIS consistently writing to the eventlog when an app crashes. I usually do get an eventlog entry when rapidfail protection kicks in and the pool is disabled. But the individual error messages that should be in the eventlog when the app crashes -- sometimes there, sometimes not.

Improve this question
2
  • Does the account the run the IIS app pool have the right permissions to write to the event log? Commented Nov 20, 2014 at 17:08
  • On the 2012 server it is running as ApplicationPoolIdentity. Not sufficient? Commented Nov 20, 2014 at 19:52

1 Answer 1

Reset to default
-1

your problem is most likely permissions related. Please have a look at this thread here and mark this as answered if you are happy with the resolution

Writing to an event log in ASP.NET on Windows Server 2008 IIS7

Thanks

Improve this answer
Sign up to request clarification or add additional context in comments.

2 Comments

I don't know why I accepted this answer now. My app doesn't (didn't) have code to write to the eventlog.
Answer unaccepted.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.