Select the product you need help with
You receive a default error message when you set custom errors in a Web application that is built on the .NET FrameworkArticle ID: 910434 - View products that this article applies to. SYMPTOMSWhen you run a Web application that is built on the Microsoft .NET Framework, you may unexpectedly receive the following generic error message even though you specified a custom error page in the Web.config file: Server Error in '/deneme1' Application. -------------------------------------------------------------------------------- Runtime Error Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed. Details: To enable the details of this specific error message to be viewable on the local server machine, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "RemoteOnly". To enable the details to be viewable on remote machines, please set "mode" to "Off". CAUSEThis issue occurs when a custom error page in the application also contains an error. RESOLUTIONTo resolve this issue, specify one of the following pages as the custom error page for the application:
STATUS This behavior is by design. MORE INFORMATIONCustom error pages in Web applications that are built on the .NET Framework are displayed only if the mode value of the customErrors element in the Web.config file is set to On or RemoteOnly. For example, you can use the following code in the Web.config file. 308132
(http://support.microsoft.com/kb/308132/
)
How to create custom error reporting pages in ASP.NET using Visual Basic .NET
306355
(http://support.microsoft.com/kb/306355/
)
How to create custom error reporting pages in ASP.NET by using Visual C# .NET
PropertiesArticle ID: 910434 - Last Review: February 10, 2006 - Revision: 1.3
|


Back to the top








