Discussion:
Problem in .Net Remoting
(too old to reply)
Latha
2008-12-23 11:03:43 UTC
Permalink
Hi All,
I am using .Net Remoting in my application. When the server and client
exe ran on the same machine, Client receives the error message as "Primary
Key Violation" if it tried to insert duplicates. But when the server on
separate machine, client receives the error message as
"System.Runtime.Remoting.RemotingException: Server encountered an internal
error. For more information, turn off customErrors in the server's .config
file." even turned off the custom errors in config. Please help me.

Thanks,
Latha.P
Phill W.
2009-01-05 13:50:10 UTC
Permalink
Post by Latha
I am using .Net Remoting in my application. When the server and client
exe ran on the same machine, Client receives the error message as "Primary
Key Violation" if it tried to insert duplicates. But when the server on
separate machine, client receives the error message as
"System.Runtime.Remoting.RemotingException: Server encountered an internal
error. For more information, turn off customErrors in the server's .config
file." even turned off the custom errors in config. Please help me.
I think that what you're seeing is that on the /single/ machine, you're
getting the actual "duplicate key" error. Across the /two/ machines,
you're getting a "custom" message put out by IIS when an unhandled
Exception gets thrown out of your code (which probably /is/ the
"duplicate key" error, but it's getting all wrapped up and hidden from
you).

#1: /Catch/ those Exceptions and return an error code from the Remoted
method instead.
#2: /If/ necessary (and it shouldn't be) turn off those "custom" error
messages (in web.config, I think).

HTH,
Phill W.

Loading...