lookup custom errors in web.config. you can define custom
error page for error 400.


>-----Original Message-----
>Hello all,
>There seems to be an issue trying to use
>ASP.NET/impersonation on a Windows 2000 Domain Controller
>with Service Pack 4. It appears that by applying Service
>Pack 4 on a Domain Controller, the IWAM account is
removed
>from the "Impersonate a client after authentication"
>policy. I haven't noticed this being an issue with other
>builds or operating systems.
>
>Web applications with this configuration will return
>an "Access Denied" with a stack trace.
>
>The fix is easy enough (add the IWAM account), but I'm
>trying to build a page to catch the error and report
>something meaningful. Unfortunately I can't seem to
catch
>the error. I have remarked out all execution paths and
>still receive the error. However I can throw a 'Foo'
>exception in the Global.asax Application_Start and halt
>the application with 'Foo'.
>
>Given that I can halt the application with my own
>exception first, I should be able to catch the "Access
>Denied" exception, but where?
>
>Thanks
>Bill
>
>.
>

Brian,
Ideally I would like to catch it in code, but thats not a bad idea.
Thanks

----- (E-Mail Removed) wrote: -----

lookup custom errors in web.config. you can define custom
error page for error 400.