Re: not working: <customErrors mode="Off"/>
- From: bruce barker <nospam@xxxxxxxxxx>
- Date: Wed, 24 Jan 2007 08:33:53 -0800
well if the error is parsing the config file, then you can turn error reporting on with the web config.
-- bruce (sqlwork.com)
Beemer Biker wrote:
I made the above change to my web.config file so that errors would be reported from a remote site as explained in the Server Error:.
Details: To enable the details of this specific error message to be viewable on remote machines, 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 "Off".
OK, this had no effect. I verifed the change to web.config did take place.
I can publish my project to my own localhost IIs, to another system running its own XP IIS.
I can even publish a FP2003 (non- aspx) app to the server that has the problem and it runs fine. I cannot get an error message from the server indicating the problem. I am publishing using local file as in \\servername\acqlib and attempting to run page using http://servername/acqlib/default.aspx
OK - to make a long story short, I got the administrator to run the page while logged onto the system and it gave an error at:
<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">
This indicates the server is not running dotnet 2.0 Admin is looking into installing dotnet 2.0 on the server.
My question: Why didnt that error message show up where I could figure out the problem myself?
- References:
- not working: <customErrors mode="Off"/>
- From: Beemer Biker
- not working: <customErrors mode="Off"/>
- Prev by Date: Re: Where do you handle your exceptions?
- Next by Date: ajax.net and cacheRolesInCookie
- Previous by thread: Re: not working: <customErrors mode="Off"/>
- Next by thread: Printing task
- Index(es):
Relevant Pages
|