Determining cause of Error in VB.NET Web Apps

  • Thread starter Thread starter Fred Nelson
  • Start date Start date
F

Fred Nelson

I'm devloping a Web Application in VB.NET. In my web.config file I have
specified that untrapped errors are to be sent to the page "errorpage.aspx".
This is working fine - if an untrapped error occurs the application is
indeed routed to this page.

On this page I would like to determine the cause of the error and either log
it in a file or send it to me via e-mail.

I am able to determine the page that sent me there from the URL parameter
"aspxerrorpath" - I would also like to be able to determine what went
wrong - or at least a line number where the failure occured.

I have the following code that I have seen in a vb.net web programming book:

dim appException as system.exception = server.getlasterror

This always returns a NULL value - no help at all!

Does anyone know how to determine the cause of an error when you have been
routed to the error page specified in the web.config file? I hope that its
possible to determine more than just the page that caused the error.

Your help would be greatly appreciated!

Fred
 
Hi Fred,

Are you handling this exception in an exception handler? It sounds like
you probably aren't. In that case, you can use the
AppDomain.UnhandledException event (and all developers should be handling
this event) to get that information.

The .NET Framework documentation contains good documentation on using this
event.

Jim Cheshire, MCSE, MCSD [MSFT]
Developer Support
ASP.NET
(e-mail address removed)

This post is provided as-is with no warranties and confers no rights.

--------------------
 
Jim:

Thanks for your help - I'll check it out!

Fred

Jim Cheshire said:
Hi Fred,

Are you handling this exception in an exception handler? It sounds like
you probably aren't. In that case, you can use the
AppDomain.UnhandledException event (and all developers should be handling
this event) to get that information.

The .NET Framework documentation contains good documentation on using this
event.

Jim Cheshire, MCSE, MCSD [MSFT]
Developer Support
ASP.NET
(e-mail address removed)

This post is provided as-is with no warranties and confers no rights.

--------------------
From: "Fred Nelson" <[email protected]>
Subject: Determining cause of Error in VB.NET Web Apps
Date: Wed, 10 Dec 2003 09:53:20 -0500
Lines: 28
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <[email protected]>
Newsgroups: microsoft.public.dotnet.framework.aspnet
NNTP-Posting-Host: syr-24-58-79-218.twcny.rr.com 24.58.79.218
Path:
Click to expand...
cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.
phx.gbl
Xref: cpmsftngxa07.phx.gbl microsoft.public.dotnet.framework.aspnet:195539
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

I'm devloping a Web Application in VB.NET. In my web.config file I have
specified that untrapped errors are to be sent to the page "errorpage.aspx".
This is working fine - if an untrapped error occurs the application is
indeed routed to this page.

On this page I would like to determine the cause of the error and either log
it in a file or send it to me via e-mail.

I am able to determine the page that sent me there from the URL parameter
"aspxerrorpath" - I would also like to be able to determine what went
wrong - or at least a line number where the failure occured.

I have the following code that I have seen in a vb.net web programming book:

dim appException as system.exception = server.getlasterror

This always returns a NULL value - no help at all!

Does anyone know how to determine the cause of an error when you have been
routed to the error page specified in the web.config file? I hope that its
possible to determine more than just the page that caused the error.

Your help would be greatly appreciated!

Fred
Click to expand...
Click to expand...
 
Fred,

Keep in mind that the ExceptionObject in the UnhandledExceptionEventArgs is
a generic Exception object.

Jim Cheshire, MCSE, MCSD [MSFT]
Developer Support
ASP.NET
(e-mail address removed)

This post is provided as-is with no warranties and confers no rights.

--------------------
From: "Fred Nelson" <[email protected]>
References: <[email protected]>
Click to expand...
Subject: Re: Determining cause of Error in VB.NET Web Apps
Date: Wed, 10 Dec 2003 12:34:18 -0500
Lines: 82
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <[email protected]>
Newsgroups: microsoft.public.dotnet.framework.aspnet
NNTP-Posting-Host: syr-24-58-79-218.twcny.rr.com 24.58.79.218
Path: cpmsftngxa07.phx.gbl!cpmsftngxa10.phx.gbl!cpmsftngxa06.phx.gbl!cpmsftngxa09.
phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11.phx.gbl
Xref: cpmsftngxa07.phx.gbl microsoft.public.dotnet.framework.aspnet:195584
X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet

Jim:

Thanks for your help - I'll check it out!

Fred

Jim Cheshire said:
Hi Fred,

Are you handling this exception in an exception handler? It sounds like
you probably aren't. In that case, you can use the
AppDomain.UnhandledException event (and all developers should be handling
this event) to get that information.

The .NET Framework documentation contains good documentation on using this
event.

Jim Cheshire, MCSE, MCSD [MSFT]
Developer Support
ASP.NET
(e-mail address removed)

This post is provided as-is with no warranties and confers no rights.

--------------------
From: "Fred Nelson" <[email protected]>
Subject: Determining cause of Error in VB.NET Web Apps
Date: Wed, 10 Dec 2003 09:53:20 -0500
Lines: 28
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <[email protected]>
Newsgroups: microsoft.public.dotnet.framework.aspnet
NNTP-Posting-Host: syr-24-58-79-218.twcny.rr.com 24.58.79.218
Path:
Click to expand...
Click to expand...
cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13
Click to expand...
 
Back
Top