But customErrors-mode IS "Off"!!!

This is not the first times this happened...
I am developing and debugging a website. I can run the site from Visual Web Developer without problems, there are no errors. However, whenever I want to see the result from a "remote computer" (or simply through another browser using the URL), I get a "censored" error message. On this page I am requested to set the CustomErrors-mode to "Off" in the web.config file if I want the error message to be visible remotely.
Done this. But the problem persists! What is going on!


<?xml version="1.0"?>
<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">
<appSettings/>
<connectionStrings/>
<system.web>
<compilation debug="true"/>
<authentication mode="Windows"/>
<!--
The <customErrors> section enables configuration
of what to do if/when an unhandled error occurs
during the execution of a request. Specifically,
it enables developers to configure html error pages
to be displayed in place of a error stack trace.
-->
<customErrors mode="Off"/>
</system.web>
</configuration>


Please help. I am at a total loss...
[1510 byte] By [FedorSteeman] at [2007-12-16]
# 1

Hi,

Are you using any authentication mode?
Check if the virtual folder has been configured as an application in IIS.

Regards,
Vikram

Vikram at 2007-9-9 > top of Msdn Tech,Visual C#,Visual C# General...
# 2
Authentication mode? I don't think so...
But I now suspect that the problem may lie in the fact that I am developing in .NET framework 2.0 and on the server they have 1.1. I have asked the administrators to upgrade (is that free by the way?)
Cheers,
Fedor
FedorSteeman at 2007-9-9 > top of Msdn Tech,Visual C#,Visual C# General...
# 3
Yes the .NET Framework v2.0 is completely free. There is a charge only on the development tools such as VS2005.

Regards,
Vikram

Vikram at 2007-9-9 > top of Msdn Tech,Visual C#,Visual C# General...
# 4

Make sure you are using the right customErrors tag. Last year, at Microsoft, I ran into a similar customer support issue where their were two different customErrors tags, one for enterprise applications, and one for web/ASP applications. Maybe the tag names were spelled differently. However, the more I think about this, the more I think it had something to do with the value. Check the case sensitivity of the values, "Off" and "On" versus "off" and "on". Also, there is the possibility that the mode settings (enterprise versus web) could be reversed between the two, like "Off" acts like "on" and "On" acts like "off". I know this sounds a bit crazy. Look at MSDN and customErrors (or customError) tags. You should find the specification for this tag as being used in more than one way.

I hope this helps.

James

jmsigler2 at 2007-9-9 > top of Msdn Tech,Visual C#,Visual C# General...
# 5
change the custom error mode to
<customErrors mode="on"/>
so that you can see the error messageSmile
krishnakishore at 2007-9-9 > top of Msdn Tech,Visual C#,Visual C# General...