HighTechTalks DotNet Forums  

.NET Remoting fails when Remote Server sends Exception

Dotnet Distributed Applications microsoft.public.dotnet.distributed_apps


Discuss .NET Remoting fails when Remote Server sends Exception in the Dotnet Distributed Applications forum.



Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old   
Jeff Levinson [mcsd]
 
Posts: n/a

Default .NET Remoting fails when Remote Server sends Exception - 06-25-2003 , 12:52 AM






I think you're working with known issue. I reported this
to Microsoft about two months ago. The situation is as
follows:
If you create a winforms app in 1.0 (and your server
objects were also done in 1.0) and you install 1.1 on the
server then your problems begin. The issue is that IIS (I
am assuming you are hosting your remote components in
IIS) automatically uses the latest version of the .NET
Framework so when it goes to serialize any messages, it
finds that the version on the client is not the same as
the version on the server and throws an exception. One
way to check and see if this is the issue, check your
output window and you should see two DIFFERENT versions
of one of the System.* libraries (I found this because
two versions of System.Data were loaded).

Microsoft is looking into this right now.

Hope this helps.

The solution is to just upgrade the winforms client to
1.1 as well and everything will work just fine.

Jeff Levinson

Author of "Building Client/Server Applications with
VB.NET: An Example Driven Approach"

Quote:
-----Original Message-----
Hello

Sending an exception from a Remote method (using .NET
Remoting TCP Channel) does not work after
installing .NET
Framework 1.1
and VS.NET 2003.

It works when the Client and Server are on the same
machine. Not if they're in different machines.


Everything works as long as the server program does not
throw an exception. If it does the client crashes
with "Server encountered an internal error. For more
information turn on customErrors in .config file..." I
did it, an no major improvements.



This is something that always worked with .NET 1.0. It
never failed.

At the present moment I'm creating a Client / Server
test
application using .NET Remoting to see how it behaves.

It returned the some error. I already check the security
configuration. This seems to be a major bug.


Does anyone experiment the some problem ?

Next step will be, return to version 1.0


LS


.


Reply With Quote
Reply




Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.