Nicholas Paldino [.NET/C# MVP]
10/29/2004 7:48:00 PM
Z D,
Have you checked the InnerException property? Because the exception
happens on another machine (and something could go wrong with the remoting
plumbing which would throw an exception) any exceptions that occur on the
server side are wrapped in a RemotingException, to distinguish the
exceptions that are thrown as a result of plumbing, instead of your code.
Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mvp@spam.guard.caspershouse.com
"Z D" <nospam@nospam.com> wrote in message
news:eyNOy8evEHA.2316@TK2MSFTNGP15.phx.gbl...
> Hello,
>
> I have a remoted object which throws an exception if something goes bad.
> eg:
> throw new Exception("Something went wrong.");
>
> When I test the assembly locally on my machine (without remoting), things
> work fine.
>
> However, once I remote the object, whenever an exception is thrown, I
> ALWAYS get the same generic exception in my try/catch block:
>
> {System.Runtime.Remoting.RemotingException}
> The message is: {Server encountered an internal error. For more
> information, turn on customErrors in the server's .config file"}
>
>
>
> Any usggestions? I've tried setting CustomErrors=on/remoteOnly/off in
> web.config but it doesn't change anything.
>
> Note: I'm using HTTP/binary remoting via IIS.
>
>
> Any suggestions/assistance would be greatly appreciated. Thanks!
>
> -ZD
>