I am having exactly the same issue. I have tried setting the TypeFilterLevel to Full as I have seen in other posts but have had no luck. Have you been able to figure this out yet?
Tom
If you're hosting in IIS, check to make sure the customErrors="Off" in the
web.config. That will allow passing of custom exceptions, not sure if that
will address the SqlError but it's worth a shot. FWIW, I've never had a
problem.
>I am having exactly the same issue. I have tried setting the
>TypeFilterLevel to Full as I have seen in other posts but have had no luck.
[quoted text clipped - 7 lines]
> Posted via DevelopmentNow.com Groups
> http://www.developmentnow.com
Mark - 21 Apr 2005 08:54 GMT
Hi Beth
No, I'm not using IIS. We've written our own remoting channel based on tcp
that uses authentication. CustomErrors is set to Off in the services config
file. And the error is being passed back as a parameter, not thrown. Seems to
be specifically a problem with SqlError - if the call to pass the exception
back fails (with the serialization error) I create a new ApplicationException
and pass that instead, without any problems - that sort of gets around the
problem, but means my client app is not able to deal with SqlErrors.
> If you're hosting in IIS, check to make sure the customErrors="Off" in the
> web.config. That will allow passing of custom exceptions, not sure if that
> will address the SqlError but it's worth a shot. FWIW, I've never had a
> problem.
Ramon de Klein - 21 Jun 2005 13:47 GMT
See my post on
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.dotnet.fra
mework.adonet&tid=e1074a25-bfcc-4147-9484-d2a67b236ee0&lang=en&cr=US&p=1.