views:

42

answers:

2

I control the code but not the server and the person at the other end knows as much about IIS as I do.

I have the classic:

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

in my root level web.config, but am not seeing error details. Could the above have been overriden by a setting at the server/application level?

A: 

Adding handling in the Application_Error event in your global.asax file could do it but that would be under your control, I would imagine.

Microsoft KB article here gives an example.

Kindness,

Dan

Daniel Elliott
There currently isn't any global.asax file being used. Thanks for the tip though.
furtive
+1  A: 

In the end the reason we weren't seeing error messages was because the machine.config file of our dev server had <deployment retail="true"/> after being cloned from our production server:

<configuration>
    <system.web>
          <deployment retail="true"/>
    </system.web>
</configuration>

It needed to be set to false. Scott Guthrie elaborates on it in his post Don’t run production ASP.NET Applications with debug=”true” enabled.

furtive