How to handle ASP.Net application Errors like failed to connect to Database

Question

5.00/5 (1 vote)

See more:

VS2005

, +

Hi everybody,

I want to handle Errors in my ASP.Net application,

Example: When try to access Database and the connection is failed, i want to go to Error Page,

I try to use web config file like that:

HTML

<customErrors mode="On" defaultRedirect="ErrorPage.aspx" />

but it not help, and the error is rasied by Visual Studio itself,

I want to see my customErrorPage.aspx is displayed when failed to connect ot database,
I tried to use try/catch block and using statement, but with all cases that
it still display either The Exception Details Yellow Screen of Death error page or The Runtime Error Yellow Screen of Death error page,
I want to know why customErrorPage.aspx not displayed

Thanks

Posted 16-Dec-11 10:57am

MrLonely_2

Updated 17-Dec-11 11:47am

v4

Add a Solution

Comments

Wonde Tadesse 16-Dec-11 17:08pm

Can you elaborate what exactly the error message you received?

2 solutions

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)

virang_21 · Answer 1 · 2011-12-16T11:35:00

There are quite a few things you can do.

1> In your code use try..catch..finally block.

C#

pulic void someFunction()
{

         try
            {
                //your business logic here
            }
         catch(Exception ex)
         {
             // Log your exception. you can use Log4Net
             throw ex;
          }
        finally
           {
              // Close your database connection here.
            }
}

2> In your Global.asax file you can log unhandled exception. I have used Log4Net Logging library.

C#

protected void Application_Error(object sender, EventArgs e)
       {
           System.Web.HttpContext context = HttpContext.Current;
           Exception ex = context.Server.GetLastError().GetBaseException();


           if (!ex.Message.Contains("Invalid length for a Base-64 char array")) // Remove invalid exception occuring in the system when user cancels the postback.
           {
               if (!(context.Request.FilePath.ToString().ToUpper().Contains(("ScriptResource.axd").ToUpper()) || context.Request.FilePath.ToString().ToUpper().Contains(("WebResource.axd").ToUpper())))
               {

                   CLogger.WriteLog(ELogLevel.ERROR, "URL : " + context.Request.Url.ToString() + "\n");

                   CLogger.WriteLog(ELogLevel.ERROR, "FILE : " + context.Request.FilePath.ToString() + "\n");

                   CLogger.WriteLog(ELogLevel.ERROR, "USER : " + context.User.Identity.Name + "\n");

                   CLogger.WriteLog(ELogLevel.ERROR, "MESSAGE : " + ex.Message + "\n");
                   CLogger.WriteLog(ELogLevel.ERROR, "SOURCE : " + ex.Source + "\n");
                   CLogger.WriteLog(ELogLevel.ERROR, "STACK TRACE : " + ex.StackTrace + "\n");
                   CLogger.WriteLog(ELogLevel.ERROR, "INNER EXCEPTION : " + ex.InnerException + "\n");
                   CLogger.WriteLog(ELogLevel.ERROR, "---------------------------------------------------------------------------------------------\n");
               }
           }





       }

for details check Clickty [^]

3> For database specific connection handling use "using statement".

4>

XML

Two things : in your web.config add

<customerrors mode="On" defaultredirect="~/Error.aspx" redirectmode="ResponseRedirect"></customerrors>

and set

<compilation debug="false">

in your production version to redirect users to error page.</compilation>

Nikil S · Answer 2 · 2011-12-16T12:48:00

Solution 2

Refer to this CP article, Error Handling in ASP.NET[^] and MSDN[^]

Posted 16-Dec-11 12:48pm

Nikil S

Updated 16-Dec-11 12:51pm

v2

Comments

thatraja 16-Dec-11 22:46pm

5!

Nikil S 17-Dec-11 6:14am

Thank you.