Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / Remoting / June 2005

Tip: Looking for answers? Try searching our database.

Serialization of SqlError fails

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Mark - 18 Apr 2005 09:27 GMT
Hi

Am using Remoting. My server PASSES an exception that includes
SqlClient.SqlError as it's inner exception to the client. When running
remoting locally on my XP Pro pc, the exception object gets to the client
without any problems.

BUT when running with the remoting service on an Windows Server 2003
machine, the passing of the exception fails with the following error:
"System.Runtime.Serialization.SerializationException: "Could not find member
name System.Data.SqlClient.SqlError".

The client and server appear to be using the same (and latest) version of
the framework, i.e. go into the .Net Configuration utility and they report
1.1.4322.573. BUT when I look at the file versions of mscorlib.dll, the
server says 1.1.4322.2300 and the XP Pro client says 1.1.4322.2032. I notice
that there are two different installation packages for the latest .Net
framework, one for Windows Server 2003 and another for the rest. Maybe this
is not part of the problem but it seems a bit odd!

Any help would be much appreciated!
tom - 20 Apr 2005 16:57 GMT
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
Beth Massi [Architect MVP] - 20 Apr 2005 20:29 GMT
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
.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.