IIS Error Page instead of Custom Error Page

I apologize - posted this in microsoft.public.internetexplorer.general but
don't know if it's a managed newsgroup. So am reposting here.

Users on same domain with same version of IE (IE 6.0 SP2) are seeing
different behavior with error pages in ASPX application.

When a handled error occurs, some users get the "custom" error page that the
application should display, while other users get

Server Error in '/BDS' Application.
--------------------------------------------------------------------------------

Runtime Error
Description: An application error occurred on the server. The current custom
error settings for this application prevent the details of the application
error from being viewed remotely (for security reasons). It could, however,
be viewed by browsers running on the local server machine.

What could be causing this? It seems it must be on the browser end...

Thanks

The error page you display does not come from IIS but ASP.Net. Your
"Custom" error page also sounds like it is configured within ASP.Net's
..config files. So, your question is really within ASP.Net and you want
to post to ASP.Net forums at www.asp.net.

If you got the below generic error message from ASP.Net, then it sounds
like your "handled error" never got handled by your application's
custom code...



//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//


BMeyer wrote:
> I apologize - posted this in microsoft.public.internetexplorer.general but
> don't know if it's a managed newsgroup. So am reposting here.
>
> Users on same domain with same version of IE (IE 6.0 SP2) are seeing
> different behavior with error pages in ASPX application.
>
> When a handled error occurs, some users get the "custom" error page that the
> application should display, while other users get
>
> Server Error in '/BDS' Application.
> --------------------------------------------------------------------------------
>
> Runtime Error
> Description: An application error occurred on the server. The current custom
> error settings for this application prevent the details of the application
> error from being viewed remotely (for security reasons). It could, however,
> be viewed by browsers running on the local server machine.
>
> What could be causing this? It seems it must be on the browser end...
>
> Thanks