Re: Calling delegate on client raises a RemotingException
From: mdb (m_b_r_a_y_at_c_t_i_u_s_a__d0t__com)
Date: 11/11/04
- Next message: Pun Law: "How to increase receive buffer in http channel?"
- Previous message: Pedro Gago: "Different servers"
- In reply to: Jeremy Chapman: "Calling delegate on client raises a RemotingException"
- Next in thread: Ken Kolda: "Re: Calling delegate on client raises a RemotingException"
- Reply: Ken Kolda: "Re: Calling delegate on client raises a RemotingException"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 11 Nov 2004 07:00:17 -0800
"Jeremy Chapman" <NoSpam@Please.com> wrote in
news:#iU6LK3xEHA.3976@TK2MSFTNGP09.phx.gbl:
> I set a delegate on my remotable object but when the server side tries
> to call the delegate method, I get the exception:
>
> System.Runtime.Remoting.RemotingException: This remoting proxy has no
> channel sink which means either the server has no registered server
> channels that are listening, or this application has no suitable
> client channel to talk to the server.
I'm new to remoting, but I'll take a stab... On your client application,
what port number are you using when you register the TcpChannel? If its
'0' (ie any available port) that might be the problem. The '0' port is
good enough for getting results of calls that you make to the server, but
its not good enough for receiving messages initiated by the server.
Register with an actual port number.
-mdb
- Next message: Pun Law: "How to increase receive buffer in http channel?"
- Previous message: Pedro Gago: "Different servers"
- In reply to: Jeremy Chapman: "Calling delegate on client raises a RemotingException"
- Next in thread: Ken Kolda: "Re: Calling delegate on client raises a RemotingException"
- Reply: Ken Kolda: "Re: Calling delegate on client raises a RemotingException"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
