Hi,

I cannot get <customErrors mode="Off"> to work at all in .Net 2.0

if I set it to 'Off' it behaves as if it was set to 'RemoteOnly' i.e. I can
see the error detail when accessing it from the local PC but not from
another machine, but if I access it from a remote machine I get the page
telling me I need to set it to Off

This isn't just on one specific application, it happens if I just create a
new blank web application in VS2005. it also happens if I deploy the app
from my dev machine (WinXP) to a server (Win2003), so it's not a problem
with the specific installation of .Net

Anyone got any clues as to what is going wrong here?

Andy

Make sure this is not overridden downstream or upstream in the machine
config file. When you change the settings, recycle the app pool - it should
be done automatically but you never know.

--

Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The O.W.C. Black Book, 2nd Edition
Exclusively on www.lulu.com/owc $19.99
-------------------------------------------------------




"Andy Fish" <ajfish [at] blueyonder.co.uk> wrote in message
news:uaNsFdxkIHA.980 [at] TK2MSFTNGP06.phx.gbl...
> Hi,
>
> I cannot get <customErrors mode="Off"> to work at all in .Net 2.0
>
> if I set it to 'Off' it behaves as if it was set to 'RemoteOnly' i.e. I
> can see the error detail when accessing it from the local PC but not from
> another machine, but if I access it from a remote machine I get the page
> telling me I need to set it to Off
>
> This isn't just on one specific application, it happens if I just create a
> new blank web application in VS2005. it also happens if I deploy the app
> from my dev machine (WinXP) to a server (Win2003), so it's not a problem
> with the specific installation of .Net
>
> Anyone got any clues as to what is going wrong here?
>
> Andy
>
>
>