404 Error Asp.net 4
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might asp.net mvc custom error page have Meta Discuss the workings and policies of this site About asp.net custom error page Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting asp.net mvc error handling 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 custom error page template programmers, just like you, helping each other. Join them; it only takes a minute: Sign up ASP.NET Web API application gives 404 when deployed at IIS 7 up vote 37 down vote favorite 19 I have an ASP.NET Web API which works fine when running on "IIS Express" with localhost:1783 But when I uncross the
Application_error
"Use IIS Express" and then press "Create Virtual Directory"... ...I just get 404 errors: Any ideas whats wrong? Thanks! asp.net iis-7 asp.net-web-api share|improve this question edited Feb 27 '14 at 20:10 rogcg 5,8611765118 asked Mar 13 '13 at 15:41 Cotten 2,88163165 whre you are setting the file path. –शेखर Mar 13 '13 at 15:52 Have you checked in you system Tray to look at Running applications on IIS express –Travis G Mar 13 '13 at 15:55 @Shekhar as I understand when clicking Create Virtual Directory, VS does this for me. i.e. Physical path seems correct, Virtual Pah is MySite1. Is the "file path" something else? –Cotten Mar 13 '13 at 15:57 add a comment| 10 Answers 10 active oldest votes up vote 52 down vote accepted I don't understand why but like said in this answer, adding runAllManagedModulesForAllRequests="true" did the trick.
you're not alone. It's surprisingly difficult to do this correctly, not helped by the fact that some errors are handled by ASP.NET and others by IIS. Ideally (and I expect such is the case with some
Global.asax Application_error
other frameworks/servers) we would just configure our custom error pages in one place and httperrors it would just work, no matter how/where the error was raised. Something like:
404 Page Not Found
I created a new ASP.NET http://benfoster.io/blog/aspnet-mvc-custom-error-pages MVC 5 application using the standard template in Visual Studio. If I run the site and try to navigate to a resource that does not exist e.g. /foo/bar, I'll get the standard ASP.NET 404 page with the following information: Server Error in '/' Application. The resource cannot be found. Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly. Requested URL: /foo/bar Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.33440 Not exactly friendly, is it? In this case the error was raised by ASP.NET MVC because it could not find a matching controller and/or action that matched the specified URL. In order to set up a custom 404 error page add the following to web.config insideresources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student Partners ISV Startups TechRewards Events Community Magazine Forums Blogs Tech Advisors Channel 9 Documentation APIs and reference Dev centers Retired content https://msdn.microsoft.com/en-us/library/bb397417.aspx 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 custom error content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Complete Example for Error Handlers Other Versions Visual Studio 2010 .NET Framework 4 Visual Studio 2008 This code example includes elements for both page-level and application-level exception handling. Code Example Files The example consists of the following files: Web.config Global.asax Default.aspx ExceptionUtility (to be put in the App_Code folder) GenericErrorPage.aspx custom error page HttpErrorPage.aspx Http404ErrorPage.aspx DefaultRedirectErrorPage.aspx Web.config The following example shows the Web.config file. The customErrors section specifies how to handle errors that occur with file types that are mapped to ASP.NET, such as .aspx, .asmx, and .ashx files. (In IIS 6.0 and in IIS 7.0 in classic mode, static content files such as .html and .jpg files are not mapped to ASP.NET.) The settings in the example customErrors section cause any unhandled HTTP 404 (file not found) errors to be directed to the Http404ErrorPage.aspx file. These HTTP 404 errors would occur if a request were made for an .aspx file, .asmx file, and so on and if the requested file did not exist. All other unhandled errors in ASP.NET files are directed to the DefaultRedirectErrorPage.aspx file. If static content files are not handled by ASP.NET, a request for a nonexistent .html or .jpg file does not cause a redirect to the Http404ErrorPage.aspx file. If you want ASP.NET to handle requests for all file types, you can configure IIS to map file-name extensions to ASP.NET. Note In the example, the mode attribute is set to "On" so that you can error messages when you run the example in Visual Studio. In a production environment, this setti