Error Handling Global.asax
resources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student Partners ISV Startups TechRewards Events Community Magazine Forums Blogs Channel 9 Documentation APIs and reference Dev centers Retired content Samples We’re sorry. The content you requested has been removed. You’ll be auto redirected in 1 second. MSDN Library MSDN Library MSDN Library MSDN Library Design Tools Development Tools and Languages Mobile and Embedded Development .NET Development Office development Online Services Open Specifications patterns & practices Servers and Enterprise Development Speech Technologies Web Development Windows Desktop App Development TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. How to: Handle Application-Level Errors Other Versions Visual Studio 2010 .NET Framework 4 Visual Studio 2008 .NET Framework 3.0 Visual Studio 2005 This code example shows how to create an error handler in the Global.asax file that will catch all unhandled ASP.NET errors while processing a request — in other words, all the errors that are not caught with a Try/Catch block or in a page-level error handler. In the example, the handler transfers control to a generic error page named GenericErrorPage.aspx, which interprets the error and displays an appropriate message. Example The following example is from a complete code sample in Complete Example for Error Handlers. Security Note Never set customErrors to Off in your Web.config file if you do not have an Application_Error handler in your Global.asax file. Potentially compromising information about your Web site can be exposed to anyone who can cause an error to occur on your site. C#VB Copy void Application_Error(object sender, EventArgs e) { // Code that runs when an unhandled error occurs // Get the exception object. Exception exc = Server.GetLastError(); // Handle HTTP errors if (exc.GetType() == typeof(HttpException)) { // The Complete Error Handling Example generates // some errors using URLs with "NoCatch" in them; // ignore these here to simulate what would happen // if a global.asax handler were not implemented. if (exc.Message.Contains("NoCatch") || exc.Message
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Catching errors in Global.asax up vote 8 down vote favorite 2 I have the following in my Global.aspx which is meant for handling errors: https://msdn.microsoft.com/en-us/library/24395wz3.aspx void Application_Error(object sender, EventArgs e) { Exception exception = Server.GetLastError(); if (exception != null) { //Log if (HttpContext.Current.Server != null) { HttpContext.Current.Server.Transfer("/siteerror.aspx"); } } } This works for the most part, but sometimes does not get into Server.Transfer. For some reason HttpContext.Current.Server is null. I figured out where this happens: when errors occur in a user control and in my business logic classes. Am I missing something here? Thanks c# asp.net error-handling share|improve this question http://stackoverflow.com/questions/10061837/catching-errors-in-global-asax edited Apr 8 '12 at 11:43 svick 124k23196308 asked Apr 8 '12 at 9:36 Peuge 71511330 2 Any reason not using Response.Redirect rather? –leppie Apr 8 '12 at 9:41 1 Where in global.asax is this? –Marc Gravell♦ Apr 8 '12 at 9:42 @leppie I did not add this so not entirely sure why the previous person chose Server.Transfer, it shouldn't make a difference though should it? –Peuge Apr 8 '12 at 9:53 @MarcGravell I have updated the question to reflect this. –Peuge Apr 8 '12 at 9:54 Earlier you use Server.blah - does Server.Transfer(...) not work? (no HttpContext.Current) –Marc Gravell♦ Apr 8 '12 at 9:56 add a comment| 2 Answers 2 active oldest votes up vote 2 down vote Application_Error block can catch exception anytime between application life cycle. Application life cycle is parent of Session life cycle as you can understand there can be many sessions within a single application. Thus you may have HttpContext.Current null at certain errors occured before creating session or after expiring of sessions. If you want to write session specific error redirects you should check for Null of current HttpContext always. You can also use Server.GetLastError to know the error details occured and write your error page redirect through CustomError tag in web.config See the following link http://weblogs.asp.net/scottgu/archive/2006/08/12/Tip_2F00_Trick_3A00_-Show-Detailed-Error-Messages-to-Developers.aspx share|i
ASP.NET Community Standup Forums Help Home/ASP.NET Forums/General ASP.NET/MVC/Error Handling in global.asax Error Handling in global.asax [Answered]RSS 8 replies Last post http://forums.asp.net/t/1505777.aspx?Error+Handling+in+global+asax Oct 27, 2011 09:51 AM by Robs030 ‹ Previous Thread|Next Thread http://www.codeproject.com/Articles/600466/ASP-NETplusApplicationplusErrorplusHandling › Print Share Twitter Facebook Email Shortcuts Active Threads Unanswered Threads Unresolved Threads Support Options Advanced Search Related Links GuidanceSamplesVideos Reply jackh None 0 Points 9 Posts Error Handling in global.asax Dec 18, 2009 03:50 PM|jackh|LINK Hi all, I'm currently trying to centralize error handling error handling in the global.asax in my asp.net MVC app. It has the following code to display a custom Error view in the default location (~/Views/Shared/Error.aspx) without using the HandleError attribute in the Controllers and specifying the
Latest Articles Latest Tips/Tricks Top Articles Beginner Articles Technical Blogs Posting/Update Guidelines Article Help Forum Article Competition Submit an article or tip Post your Blog quick answersQ&A Ask a Question about this article Ask a Question View Unanswered Questions View All Questions... C# questions Linux questions ASP.NET questions SQL questions VB.NET questions discussionsforums All Message Boards... Application Lifecycle> Running a Business Sales / Marketing Collaboration / Beta Testing Work Issues Design and Architecture ASP.NET JavaScript C / C++ / MFC> ATL / WTL / STL Managed C++/CLI C# Free Tools Objective-C and Swift Database Hardware & Devices> System Admin Hosting and Servers Java .NET Framework Android iOS Mobile SharePoint Silverlight / WPF Visual Basic Web Development Site Bugs / Suggestions Spam and Abuse Watch features Competitions News The Insider Newsletter The Daily Build Newsletter Newsletter archive Surveys Product Showcase Research Library CodeProject Stuff communitylounge Who's Who Most Valuable Professionals The Lounge The Insider News The Weird & The Wonderful The Soapbox Press Releases Non-English Language > General Indian Topics General Chinese Topics help What is 'CodeProject'? General FAQ Ask a Question Bugs and Suggestions Article Help Forum Site Map Advertise with us About our Advertising Employment Opportunities About Us Articles » Web Development » ASP.NET » General ArticleBrowse CodeStatsRevisions (9)Alternatives Comments (37) Add your ownalternative version Tagged as HTMLC#VS2013ASP.NET Stats 112.2K views2.6K downloads90 bookmarked Posted 30 May 2013 ASP.NET Application Error Handling Daniel Miller, 26 Jan 2015 CPOL 4.95 (37 votes) 1 2 3 4 5 4.95/5 - 37 votesμ 4.95, σa 1.05 [?] Rate this: Please Sign up or sign in to vote. Application error handling in ASP.NET Download demo - 269.4 KB Introduction When an unhandled exception occurs in my application, I want my application to give the user a "graceful" response. Regardless of the error, I do not want the user to see an unfriendly technical error messages generated by IIS or ASP.NET. At the same time, I want to receive email notification for every unhandled exception. This article describes a simple and comprehensive solution to this problem. The Problem When I have no error handling configured for my a