Shut off unhandled error function so error throws at source

Question

0.00/5 (No votes)

See more:

Hi, all. Could you please help with a question?

Problem: Application_Error function catches an unhandled error, but offers insufficient information to identify the source problem code.

Question: How can I shut off this error handling so that the error stops debugging at the source?

Environment: Visual Studio 2022; An ASP web app written in C#. Data is from a SQL Server.

Thanks!

What I have tried:

Background: I haven't coded web pages or C# in many years. I've been handed a charitable giving web solution to take over. I need to add giving paid-time-off hours. I'm copying the cash elements and changing cash to PTO.

When I do this, sometimes everything works. Other times, I hit this frustrating error which doesn't tell me where the problem came from. Instead, it stops in the Application_Error function.

At this point, you'll likely say, "What's the Error." I'd rather not say, since that will lead down a rabbit hole of trying to debug that specific error. Instead, I'd like the debugging to bomb out at the source, not in the unhandled error function.

Thanks!

Posted 12-Apr-23 3:42am

ScottScott

Updated 12-Apr-23 4:03am

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2023-04-12T04:03:00

I haven't tried it - I don't have a web page project handy - but you should be able to edit the Global.aspx file and add what code you want to that - there you can pick up the last error object and that should contain the info you need in terms of the exception object: How to Handle Application_error in ASP.NET App's Global.asax[^]
The Exception object can contain InnerException details as well as the file, line and stack trace where the error occurred.
Then you can add individual try...catch blocks to narrow down the problem as needed.