Re: RemotingExceptions: turn on "customErrors" in the server's config file???

[Paulo Lisboa]

customErrors="true" isn't a valid option, the possible options are
[On|Off|RemoteOnly]

For security reasons, I suggest you configure as this:
customErrors="RemoteOnly"

The configuration above tells that errors can be fully displayed if your
browser is running on the same box where your WebApplication is hosted.
Otherwise, if the browser is running in some other box then ASPNET will
suppress details about the error. This is an interesting behavior because
when you are developing very often your browser and server are the same box
(and you want to see all error details), but when you deploy to production
you don't want your customers to see details (e.g. comments, code, etc.)
whenever an exception is thrown in the server app. Notice that even comments
in a code may contain private information that you may prefer to keep
private.

Otherwise, if you don't care about privacy for your code, you can also set
customErrors="Off" ,
However, I strongly discourage this practice.

--
Thanks.
Paulo

DISCLAIMER: This posting is provided "AS IS" with no warranties, and confers
no rights. Use of any possible included code samples are subject to the
terms specified at http://www.microsoft.com/info/cpyright.htm"

 

[0to60]

The configuration above tells that errors can be fully displayed if your
browser is running on the same box where your WebApplication is hosted.
Otherwise, if the browser is running in some other box then ASPNET will
suppress details about the error. This is an interesting behavior because
when you are developing very often your browser and server are the same box
(and you want to see all error details), but when you deploy to production
you don't want your customers to see details (e.g. comments, code, etc.)
whenever an exception is thrown in the server app. Notice that even comments
in a code may contain private information that you may prefer to keep
private.

This is NOT a web service! This is a regular app that uses remoting! This
has absolutely nothing to do with browsers, ASP.NET, web servers, IIS, none
of that. This is a peer to peer distributed app.

 

[Paulo Lisboa [MSFT]]

Once I am not debugging your code I can only guess:
My guess is that this exception is being thrown by your Remoting server, it
then gets propagated to your client app, which must be a WinForm app or
Console app and this client app is the one popping-up some dialog box with
the exception that came from the Remoting server. In this case, you need to
check how customError is configured in your Remoting Server. If this isn't
the case, I don't have any other suggestion.

--
Thanks.
Paulo

DISCLAIMER: This posting is provided "AS IS" with no warranties, and confers
no rights. Use of any included code samples are subject to the terms
specified at http://www.microsoft.com/info/cpyright.htm"