Re: How To Create Custom Aspx Error Reporting Page
From: John Lau (johnlau_at_olc.ubc.ca)
Date: 02/26/04
- Next message: Don: "Re: Keeping objects between requests within the same session"
- Previous message: JackV: "Re: New to ASP.NET but oldtime ASP classic developer"
- In reply to: Steven Cheng[MSFT]: "Re: How To Create Custom Aspx Error Reporting Page"
- Next in thread: John Lau: "Re: How To Create Custom Aspx Error Reporting Page"
- Reply: John Lau: "Re: How To Create Custom Aspx Error Reporting Page"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 26 Feb 2004 13:22:37 -0800
Hi Steve and Bill,
Yes, Steve, you have described my exact problem. Thank you! And thanks to
Bill for taking an interest in my problem.
Before I saw your posting, I took Bill's suggestion and created a simple
error handling sample. It worked! Then I had to find the cause within the
difference between his sample and my application, which was considerable.
The first thing I tried was to copy my Web.config file into the simple
sample. This duplicated my problem. Then I removed the authorization
section, and the problem again disappeared. As you said, I am using
formauthentication, and the problem was:
<authorization>
<deny users="?" />
<allow users="*" />
</authorization>
I was going to try and further isolate the problem today, but your
explanation made that unnecessary.
Since I don't want a new session, I am using Server.Transfer. One other
problem I am encountering is that occasionally, after changing some code, I
will get the following error. If I reboot, the error goes away. Any way of
getting rid of the error without rebooting?
Thanks,
John
Server Error in '/WebDemo' 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".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="RemoteOnly"/>
</system.web>
</configuration>
Notes: The current error page you are seeing can be replaced by a custom
error page by modifying the "defaultRedirect" attribute of the application's
<customErrors> configuration tag to point to a custom error page URL.
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="On" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
- Next message: Don: "Re: Keeping objects between requests within the same session"
- Previous message: JackV: "Re: New to ASP.NET but oldtime ASP classic developer"
- In reply to: Steven Cheng[MSFT]: "Re: How To Create Custom Aspx Error Reporting Page"
- Next in thread: John Lau: "Re: How To Create Custom Aspx Error Reporting Page"
- Reply: John Lau: "Re: How To Create Custom Aspx Error Reporting Page"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|