Asp Forum - SocketException at GetLifetimeService - microsoft.public.dotnet.framework.remoting

Chadi Zwein

6/29/2004 1:45:00 PM

This is a CAO scenario with lifetime management.
The remote objects are created successfully!! (no exceptions).

Following that, and in the function calling
RemotingServices.GetLifetimeService on the remote object, a
System.Net.Sockets.SocketException occurs, complaining that the server did
not respond in a timely fashion or the connection to the server was reset...

Server Stack Trace:
at System.Net.Sockets.Socket.Connect(EndPoint remote EP)
at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket()
at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String
machineAndPort)
:
:
Exception Rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy...
:
at System.Runtime.MarshalByRefObject.GetLifetimeService()
at MyFunction()

This error is occurring on exactly 1 testing site among 40 to 50 ones, but
it always appears there. Nothing interesting in the event logs, and the IP
configuration of both (Windows 2000 SP4) client and server machines is very
basic. No firewalls involved.

Any idea?

12 Answers

Sunny

6/29/2004 2:21:00 PM

Hi,
can you post some code?

And what happens, if you create a remote object and try to execute a
method on it, without invoking GetLifetimeService?

Sunny

In article <enVnt#dXEHA.3668@TK2MSFTNGP09.phx.gbl>, zwein@hotmail.com_
says...
> This is a CAO scenario with lifetime management.
> The remote objects are created successfully!! (no exceptions).
>
> Following that, and in the function calling
> RemotingServices.GetLifetimeService on the remote object, a
> System.Net.Sockets.SocketException occurs, complaining that the server did
> not respond in a timely fashion or the connection to the server was reset...
>
> Server Stack Trace:
> at System.Net.Sockets.Socket.Connect(EndPoint remote EP)
> at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket()
> at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String
> machineAndPort)
> :
> :
> Exception Rethrown at [0]:
> at System.Runtime.Remoting.Proxies.RealProxy...
> :
> at System.Runtime.MarshalByRefObject.GetLifetimeService()
> at MyFunction()
>
>
> This error is occurring on exactly 1 testing site among 40 to 50 ones, but
> it always appears there. Nothing interesting in the event logs, and the IP
> configuration of both (Windows 2000 SP4) client and server machines is very
> basic. No firewalls involved.
>
> Any idea?
>
>
>

Allen Anderson

6/29/2004 4:20:00 PM

does this one site have any special firewalls or anything different
about its network configuration?

Allen Anderson
http://www.glacialcomp...
mailto: allen@put my website base here.com

On Tue, 29 Jun 2004 16:44:42 +0300, "Chadi Zwein" <zwein@hotmail.com_>
wrote:

>This is a CAO scenario with lifetime management.
>The remote objects are created successfully!! (no exceptions).
>
>Following that, and in the function calling
>RemotingServices.GetLifetimeService on the remote object, a
>System.Net.Sockets.SocketException occurs, complaining that the server did
>not respond in a timely fashion or the connection to the server was reset...
>
>Server Stack Trace:
>at System.Net.Sockets.Socket.Connect(EndPoint remote EP)
>at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket()
>at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String
>machineAndPort)
>:
>:
>Exception Rethrown at [0]:
>at System.Runtime.Remoting.Proxies.RealProxy...
>:
>at System.Runtime.MarshalByRefObject.GetLifetimeService()
>at MyFunction()
>
>
>This error is occurring on exactly 1 testing site among 40 to 50 ones, but
>it always appears there. Nothing interesting in the event logs, and the IP
>configuration of both (Windows 2000 SP4) client and server machines is very
>basic. No firewalls involved.
>
>Any idea?
>

Chadi Zwein

6/30/2004 2:39:00 PM

I''ll try to do that. The problem is that the error is only occuring in a
test site located far in Germany!
In the meantime here is some usefule code:

thx

try
{
// initialize the state machine
remoteObjects = this.CreateRemoteObject();
if((remoteObjects.adminObject == null)||(remoteObjects.sponsorObject ==
null))
return false;

//Activate the renewal mechanism
instanceSponsor = (InstanceSponsor)remoteObjects.sponsorObject;
serverLease =
(ILease)RemotingServices.GetLifetimeService((MarshalByRefObject)remoteObject
s.adminObject);
serverLease.Register((ISponsor)instanceSponsor);
}
catch(Exception e)
{
errorNumber = (long)ErrorCollection.CreateCredential_CreateRemoteObject;
errorDescription = e.Message;
}

private RemoteObjects CreateRemoteObject()
{
try
{
//setting up the transfer channel and creating the object
TcpClientChannel clientChannel = new TcpClientChannel("", new
BinaryClientFormatterSinkProvider());
channel = clientChannel as IChannel;
ChannelServices.RegisterChannel(channel);

object[] attrs = {new UrlAttribute(this.serverURL)};
ObjectHandle oh =
Activator.CreateInstance("SE.Admin.Server","SE.Admin.Server.AdminServer",att
rs);
object sponsorObj =
Activator.GetObject(typeof(SE.Admin.Server.InstanceSponsor),
this.sponsorURL);
object adminObj = oh.Unwrap();

return new RemoteObjects(adminObj, sponsorObj);
}
catch(Exception e)
{
Debug.WriteLine(e.ToString());
throw e;
}
}

"Sunny" <sunnyask@icebergwireless.com> wrote in message
news:OVOEJReXEHA.2520@TK2MSFTNGP12.phx.gbl...
> Hi,
> can you post some code?
>
> And what happens, if you create a remote object and try to execute a
> method on it, without invoking GetLifetimeService?
>
>
> Sunny
>
>
> In article <enVnt#dXEHA.3668@TK2MSFTNGP09.phx.gbl>, zwein@hotmail.com_
> says...
> > This is a CAO scenario with lifetime management.
> > The remote objects are created successfully!! (no exceptions).
> >
> > Following that, and in the function calling
> > RemotingServices.GetLifetimeService on the remote object, a
> > System.Net.Sockets.SocketException occurs, complaining that the server
did
> > not respond in a timely fashion or the connection to the server was
reset...
> >
> > Server Stack Trace:
> > at System.Net.Sockets.Socket.Connect(EndPoint remote EP)
> > at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket()
> > at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String
> > machineAndPort)
> > :
> > :
> > Exception Rethrown at [0]:
> > at System.Runtime.Remoting.Proxies.RealProxy...
> > :
> > at System.Runtime.MarshalByRefObject.GetLifetimeService()
> > at MyFunction()
> >
> >
> > This error is occurring on exactly 1 testing site among 40 to 50 ones,
but
> > it always appears there. Nothing interesting in the event logs, and the
IP
> > configuration of both (Windows 2000 SP4) client and server machines is
very
> > basic. No firewalls involved.
> >
> > Any idea?
> >
> >
> >

Chadi Zwein

6/30/2004 2:43:00 PM

No firewalls are invloved.
Here is the (very usual) IP configuration reported from the test site:

======================================
CLIENT PC
======================================

C:\Dokumente und Einstellungen\TM-Admin>ipconfig /all

Windows 2000-IP-Konfiguration

Hostname. . . . . . . . . . . . . : TM-PC1
Primäres DNS-Suffix . . . . . . . : tm-consulting.de
Knotentyp . . . . . . . . . . . . : Broadcastadapter
IP-Routing aktiviert. . . . . . . : Nein
WINS-Proxy aktiviert. . . . . . . : Nein
DNS-Suffixsuchliste . . . . . . . : tm-consulting.de

Ethernetadapter "LAN-Verbindung":

Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connecti
on
Physikalische Adresse . . . . . . : 00-03-47-DC-FE-91
DHCP-aktiviert. . . . . . . . . . : Nein
IP-Adresse. . . . . . . . . . . . : 192.168.1.10
Subnetzmaske. . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . : 192.168.1.254
DNS-Server. . . . . . . . . . . . : 192.168.1.250

======================================
SERVER PC
======================================

C:\Dokumente und Einstellungen\tm-admin>ipconfig /all

Windows 2000-IP-Konfiguration

Hostname. . . . . . . . . . . . . : tmc-srv01
Primäres DNS-Suffix . . . . . . . : tm-consulting.de
Knotentyp . . . . . . . . . . . . : Broadcastadapter
IP-Routing aktiviert. . . . . . . : Nein
WINS-Proxy aktiviert. . . . . . . : Nein
DNS-Suffixsuchliste . . . . . . . : tm-consulting.de

Ethernetadapter "LAN-Verbindung 2":

Medienstatus. . . . . . . . . . . : Kabel nicht angeschlossen
Beschreibung. . . . . . . . . . . : Intel(R) PRO/100 S Desktop
Adapter
Physikalische Adresse . . . . . . : 00-02-B3-88-AC-81

Ethernetadapter "LAN-Verbindung":

Verbindungsspezifisches DNS-Suffix:
Beschreibung. . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connecti
on
Physikalische Adresse . . . . . . : 00-03-47-C2-BE-86
DHCP-aktiviert. . . . . . . . . . : Nein
IP-Adresse. . . . . . . . . . . . : 192.168.1.250
Subnetzmaske. . . . . . . . . . . : 255.255.255.0
Standardgateway . . . . . . . . . : 192.168.1.254
DNS-Server. . . . . . . . . . . . : 192.168.1.250

"Allen Anderson" <allen@sparkysystems.com> wrote in message
news:mj53e0d5b7amg37daj6bth6o1291ccn006@4ax.com...
> does this one site have any special firewalls or anything different
> about its network configuration?
>
> Allen Anderson
> http://www.glacialcomp...
> mailto: allen@put my website base here.com
>
> On Tue, 29 Jun 2004 16:44:42 +0300, "Chadi Zwein" <zwein@hotmail.com_>
> wrote:
>
> >This is a CAO scenario with lifetime management.
> >The remote objects are created successfully!! (no exceptions).
> >
> >Following that, and in the function calling
> >RemotingServices.GetLifetimeService on the remote object, a
> >System.Net.Sockets.SocketException occurs, complaining that the server
did
> >not respond in a timely fashion or the connection to the server was
reset...
> >
> >Server Stack Trace:
> >at System.Net.Sockets.Socket.Connect(EndPoint remote EP)
> >at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket()
> >at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String
> >machineAndPort)
> >:
> >:
> >Exception Rethrown at [0]:
> >at System.Runtime.Remoting.Proxies.RealProxy...
> >:
> >at System.Runtime.MarshalByRefObject.GetLifetimeService()
> >at MyFunction()
> >
> >
> >This error is occurring on exactly 1 testing site among 40 to 50 ones,
but
> >it always appears there. Nothing interesting in the event logs, and the
IP
> >configuration of both (Windows 2000 SP4) client and server machines is
very
> >basic. No firewalls involved.
> >
> >Any idea?
> >
>

Chadi Zwein

6/30/2004 2:49:00 PM

What is bothering me is that why would a SocketException occur on the call
to GetLifetimeService and not while creating the remote objects??

Furthermore, the SocketException is on the server; what is the server trying
to connect to?
Probably itself (Lease Manager<==>CAO), but why would then this fail?

Any idea?

"Chadi Zwein" <zwein@hotmail.com_> wrote in message
news:enVnt%23dXEHA.3668@TK2MSFTNGP09.phx.gbl...
> This is a CAO scenario with lifetime management.
> The remote objects are created successfully!! (no exceptions).
>
> Following that, and in the function calling
> RemotingServices.GetLifetimeService on the remote object, a
> System.Net.Sockets.SocketException occurs, complaining that the server did
> not respond in a timely fashion or the connection to the server was
reset...
>
> Server Stack Trace:
> at System.Net.Sockets.Socket.Connect(EndPoint remote EP)
> at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket()
> at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String
> machineAndPort)
> :
> :
> Exception Rethrown at [0]:
> at System.Runtime.Remoting.Proxies.RealProxy...
> :
> at System.Runtime.MarshalByRefObject.GetLifetimeService()
> at MyFunction()
>
>
> This error is occurring on exactly 1 testing site among 40 to 50 ones, but
> it always appears there. Nothing interesting in the event logs, and the IP
> configuration of both (Windows 2000 SP4) client and server machines is
very
> basic. No firewalls involved.
>
> Any idea?
>
>

Ken Kolda

6/30/2004 4:21:00 PM

I don''t know if this will help but I''ve seen similar problems in the past
caused by having a disconnected network adapter (which I see you have on
your server). Try disabling the unused network adapter on the server and
give it another shot.

Ken

"Chadi Zwein" <zwein@hotmail.com_> wrote in message
news:uoklyDrXEHA.1656@TK2MSFTNGP09.phx.gbl...
> No firewalls are invloved.
> Here is the (very usual) IP configuration reported from the test site:
>
> ======================================
> CLIENT PC
> ======================================
>
> C:\Dokumente und Einstellungen\TM-Admin>ipconfig /all
>
> Windows 2000-IP-Konfiguration
>
> Hostname. . . . . . . . . . . . . : TM-PC1
> Primäres DNS-Suffix . . . . . . . : tm-consulting.de
> Knotentyp . . . . . . . . . . . . : Broadcastadapter
> IP-Routing aktiviert. . . . . . . : Nein
> WINS-Proxy aktiviert. . . . . . . : Nein
> DNS-Suffixsuchliste . . . . . . . : tm-consulting.de
>
> Ethernetadapter "LAN-Verbindung":
>
> Verbindungsspezifisches DNS-Suffix:
> Beschreibung. . . . . . . . . . . : Intel(R) PRO/100 VE Network
> Connecti
> on
> Physikalische Adresse . . . . . . : 00-03-47-DC-FE-91
> DHCP-aktiviert. . . . . . . . . . : Nein
> IP-Adresse. . . . . . . . . . . . : 192.168.1.10
> Subnetzmaske. . . . . . . . . . . : 255.255.255.0
> Standardgateway . . . . . . . . . : 192.168.1.254
> DNS-Server. . . . . . . . . . . . : 192.168.1.250
>
>
>
>
> ======================================
> SERVER PC
> ======================================
>
> C:\Dokumente und Einstellungen\tm-admin>ipconfig /all
>
> Windows 2000-IP-Konfiguration
>
> Hostname. . . . . . . . . . . . . : tmc-srv01
> Primäres DNS-Suffix . . . . . . . : tm-consulting.de
> Knotentyp . . . . . . . . . . . . : Broadcastadapter
> IP-Routing aktiviert. . . . . . . : Nein
> WINS-Proxy aktiviert. . . . . . . : Nein
> DNS-Suffixsuchliste . . . . . . . : tm-consulting.de
>
> Ethernetadapter "LAN-Verbindung 2":
>
> Medienstatus. . . . . . . . . . . : Kabel nicht angeschlossen
> Beschreibung. . . . . . . . . . . : Intel(R) PRO/100 S Desktop
> Adapter
> Physikalische Adresse . . . . . . : 00-02-B3-88-AC-81
>
> Ethernetadapter "LAN-Verbindung":
>
> Verbindungsspezifisches DNS-Suffix:
> Beschreibung. . . . . . . . . . . : Intel(R) PRO/100 VE Network
> Connecti
> on
> Physikalische Adresse . . . . . . : 00-03-47-C2-BE-86
> DHCP-aktiviert. . . . . . . . . . : Nein
> IP-Adresse. . . . . . . . . . . . : 192.168.1.250
> Subnetzmaske. . . . . . . . . . . : 255.255.255.0
> Standardgateway . . . . . . . . . : 192.168.1.254
> DNS-Server. . . . . . . . . . . . : 192.168.1.250
>
>
>
> "Allen Anderson" <allen@sparkysystems.com> wrote in message
> news:mj53e0d5b7amg37daj6bth6o1291ccn006@4ax.com...
> > does this one site have any special firewalls or anything different
> > about its network configuration?
> >
> > Allen Anderson
> > http://www.glacialcomp...
> > mailto: allen@put my website base here.com
> >
> > On Tue, 29 Jun 2004 16:44:42 +0300, "Chadi Zwein" <zwein@hotmail.com_>
> > wrote:
> >
> > >This is a CAO scenario with lifetime management.
> > >The remote objects are created successfully!! (no exceptions).
> > >
> > >Following that, and in the function calling
> > >RemotingServices.GetLifetimeService on the remote object, a
> > >System.Net.Sockets.SocketException occurs, complaining that the server
> did
> > >not respond in a timely fashion or the connection to the server was
> reset...
> > >
> > >Server Stack Trace:
> > >at System.Net.Sockets.Socket.Connect(EndPoint remote EP)
> > >at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket()
> > >at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String
> > >machineAndPort)
> > >:
> > >:
> > >Exception Rethrown at [0]:
> > >at System.Runtime.Remoting.Proxies.RealProxy...
> > >:
> > >at System.Runtime.MarshalByRefObject.GetLifetimeService()
> > >at MyFunction()
> > >
> > >
> > >This error is occurring on exactly 1 testing site among 40 to 50 ones,
> but
> > >it always appears there. Nothing interesting in the event logs, and the
> IP
> > >configuration of both (Windows 2000 SP4) client and server machines is
> very
> > >basic. No firewalls involved.
> > >
> > >Any idea?
> > >
> >
>
>

Sunny

6/30/2004 4:55:00 PM

Hi Chadi,

as Ken suggested, you have no control on which adapter the server will
try to bind for the replay. With your disconnected adapter, server just
tries to send a replay using the disconnected one, and it fails.

Also, when you invoke Activator.CreateInstance, no network connection is
made. The connection is established on the first method invocation, in
your case this is GetLifetime...

You can try what Ken suggested, or you can use bindTo property for the
server channel, so you are sure that the server always uses the right
interface.

Hope that helps

Sunny

In article <u1ZHcHrXEHA.2944@TK2MSFTNGP11.phx.gbl>, zwein@hotmail.com_
says...
> What is bothering me is that why would a SocketException occur on the call
> to GetLifetimeService and not while creating the remote objects??
>
> Furthermore, the SocketException is on the server; what is the server trying
> to connect to?
> Probably itself (Lease Manager<==>CAO), but why would then this fail?
>
> Any idea?
>
> "Chadi Zwein" <zwein@hotmail.com_> wrote in message
> news:enVnt%23dXEHA.3668@TK2MSFTNGP09.phx.gbl...
> > This is a CAO scenario with lifetime management.
> > The remote objects are created successfully!! (no exceptions).
> >
> > Following that, and in the function calling
> > RemotingServices.GetLifetimeService on the remote object, a
> > System.Net.Sockets.SocketException occurs, complaining that the server did
> > not respond in a timely fashion or the connection to the server was
> reset...
> >
> > Server Stack Trace:
> > at System.Net.Sockets.Socket.Connect(EndPoint remote EP)
> > at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket()
> > at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String
> > machineAndPort)
> > :
> > :
> > Exception Rethrown at [0]:
> > at System.Runtime.Remoting.Proxies.RealProxy...
> > :
> > at System.Runtime.MarshalByRefObject.GetLifetimeService()
> > at MyFunction()
> >
> >
> > This error is occurring on exactly 1 testing site among 40 to 50 ones, but
> > it always appears there. Nothing interesting in the event logs, and the IP
> > configuration of both (Windows 2000 SP4) client and server machines is
> very
> > basic. No firewalls involved.
> >
> > Any idea?
> >
> >
>
>
>

Chadi Zwein

7/2/2004 9:54:00 AM

I''ll surely try that.
I was kind of looking for a "multihomed" issue on the server but I did not
notice the unplugged interface on the server.

We''ll see...

"Ken Kolda" <ken.kolda@elliemae-nospamplease.com> wrote in message
news:u$6un5rXEHA.3044@TK2MSFTNGP09.phx.gbl...
> I don''t know if this will help but I''ve seen similar problems in the past
> caused by having a disconnected network adapter (which I see you have on
> your server). Try disabling the unused network adapter on the server and
> give it another shot.
>
> Ken
>
>
> "Chadi Zwein" <zwein@hotmail.com_> wrote in message
> news:uoklyDrXEHA.1656@TK2MSFTNGP09.phx.gbl...
> > No firewalls are invloved.
> > Here is the (very usual) IP configuration reported from the test site:
> >
> > ======================================
> > CLIENT PC
> > ======================================
> >
> > C:\Dokumente und Einstellungen\TM-Admin>ipconfig /all
> >
> > Windows 2000-IP-Konfiguration
> >
> > Hostname. . . . . . . . . . . . . : TM-PC1
> > Primäres DNS-Suffix . . . . . . . : tm-consulting.de
> > Knotentyp . . . . . . . . . . . . : Broadcastadapter
> > IP-Routing aktiviert. . . . . . . : Nein
> > WINS-Proxy aktiviert. . . . . . . : Nein
> > DNS-Suffixsuchliste . . . . . . . : tm-consulting.de
> >
> > Ethernetadapter "LAN-Verbindung":
> >
> > Verbindungsspezifisches DNS-Suffix:
> > Beschreibung. . . . . . . . . . . : Intel(R) PRO/100 VE Network
> > Connecti
> > on
> > Physikalische Adresse . . . . . . : 00-03-47-DC-FE-91
> > DHCP-aktiviert. . . . . . . . . . : Nein
> > IP-Adresse. . . . . . . . . . . . : 192.168.1.10
> > Subnetzmaske. . . . . . . . . . . : 255.255.255.0
> > Standardgateway . . . . . . . . . : 192.168.1.254
> > DNS-Server. . . . . . . . . . . . : 192.168.1.250
> >
> >
> >
> >
> > ======================================
> > SERVER PC
> > ======================================
> >
> > C:\Dokumente und Einstellungen\tm-admin>ipconfig /all
> >
> > Windows 2000-IP-Konfiguration
> >
> > Hostname. . . . . . . . . . . . . : tmc-srv01
> > Primäres DNS-Suffix . . . . . . . : tm-consulting.de
> > Knotentyp . . . . . . . . . . . . : Broadcastadapter
> > IP-Routing aktiviert. . . . . . . : Nein
> > WINS-Proxy aktiviert. . . . . . . : Nein
> > DNS-Suffixsuchliste . . . . . . . : tm-consulting.de
> >
> > Ethernetadapter "LAN-Verbindung 2":
> >
> > Medienstatus. . . . . . . . . . . : Kabel nicht angeschlossen
> > Beschreibung. . . . . . . . . . . : Intel(R) PRO/100 S Desktop
> > Adapter
> > Physikalische Adresse . . . . . . : 00-02-B3-88-AC-81
> >
> > Ethernetadapter "LAN-Verbindung":
> >
> > Verbindungsspezifisches DNS-Suffix:
> > Beschreibung. . . . . . . . . . . : Intel(R) PRO/100 VE Network
> > Connecti
> > on
> > Physikalische Adresse . . . . . . : 00-03-47-C2-BE-86
> > DHCP-aktiviert. . . . . . . . . . : Nein
> > IP-Adresse. . . . . . . . . . . . : 192.168.1.250
> > Subnetzmaske. . . . . . . . . . . : 255.255.255.0
> > Standardgateway . . . . . . . . . : 192.168.1.254
> > DNS-Server. . . . . . . . . . . . : 192.168.1.250
> >
> >
> >
> > "Allen Anderson" <allen@sparkysystems.com> wrote in message
> > news:mj53e0d5b7amg37daj6bth6o1291ccn006@4ax.com...
> > > does this one site have any special firewalls or anything different
> > > about its network configuration?
> > >
> > > Allen Anderson
> > > http://www.glacialcomp...
> > > mailto: allen@put my website base here.com
> > >
> > > On Tue, 29 Jun 2004 16:44:42 +0300, "Chadi Zwein" <zwein@hotmail.com_>
> > > wrote:
> > >
> > > >This is a CAO scenario with lifetime management.
> > > >The remote objects are created successfully!! (no exceptions).
> > > >
> > > >Following that, and in the function calling
> > > >RemotingServices.GetLifetimeService on the remote object, a
> > > >System.Net.Sockets.SocketException occurs, complaining that the
server
> > did
> > > >not respond in a timely fashion or the connection to the server was
> > reset...
> > > >
> > > >Server Stack Trace:
> > > >at System.Net.Sockets.Socket.Connect(EndPoint remote EP)
> > > >at
System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket()
> > > >at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String
> > > >machineAndPort)
> > > >:
> > > >:
> > > >Exception Rethrown at [0]:
> > > >at System.Runtime.Remoting.Proxies.RealProxy...
> > > >:
> > > >at System.Runtime.MarshalByRefObject.GetLifetimeService()
> > > >at MyFunction()
> > > >
> > > >
> > > >This error is occurring on exactly 1 testing site among 40 to 50
ones,
> > but
> > > >it always appears there. Nothing interesting in the event logs, and
the
> > IP
> > > >configuration of both (Windows 2000 SP4) client and server machines
is
> > very
> > > >basic. No firewalls involved.
> > > >
> > > >Any idea?
> > > >
> > >
> >
> >
>
>

Allen Anderson

7/6/2004 3:16:00 AM

I''ve run into problems with remoting where the line was disconnected
too as some others have mentioned. There are also issues with
multi-homed servers. I wrote an article that talks about multi-homed
servers with CAO objects but I haven''t tried it with SAO objects as of
yet. You can check it out here.

http://www.glacialcomp.../ArticleDetail.aspx?artic...

Beyond that, you might add a loopback adapter to the machines. I''ve
found this seems to mitigate some problems when a primary network
adapter is disconnected or disabled for one reason or another.

Cheers,
Allen Anderson
http://www.glacialcomp...
mailto: allen@put my website base here.com

On Wed, 30 Jun 2004 17:42:39 +0300, "Chadi Zwein" <zwein@hotmail.com_>
wrote:

>No firewalls are invloved.
>Here is the (very usual) IP configuration reported from the test site:
>
>======================================
>CLIENT PC
>======================================
>
>C:\Dokumente und Einstellungen\TM-Admin>ipconfig /all
>
>Windows 2000-IP-Konfiguration
>
> Hostname. . . . . . . . . . . . . : TM-PC1
> PrimÃ¤res DNS-Suffix . . . . . . . : tm-consulting.de
> Knotentyp . . . . . . . . . . . . : Broadcastadapter
> IP-Routing aktiviert. . . . . . . : Nein
> WINS-Proxy aktiviert. . . . . . . : Nein
> DNS-Suffixsuchliste . . . . . . . : tm-consulting.de
>
>Ethernetadapter "LAN-Verbindung":
>
> Verbindungsspezifisches DNS-Suffix:
> Beschreibung. . . . . . . . . . . : Intel(R) PRO/100 VE Network
>Connecti
>on
> Physikalische Adresse . . . . . . : 00-03-47-DC-FE-91
> DHCP-aktiviert. . . . . . . . . . : Nein
> IP-Adresse. . . . . . . . . . . . : 192.168.1.10
> Subnetzmaske. . . . . . . . . . . : 255.255.255.0
> Standardgateway . . . . . . . . . : 192.168.1.254
> DNS-Server. . . . . . . . . . . . : 192.168.1.250
>
>
>
>
>======================================
>SERVER PC
>======================================
>
>C:\Dokumente und Einstellungen\tm-admin>ipconfig /all
>
>Windows 2000-IP-Konfiguration
>
> Hostname. . . . . . . . . . . . . : tmc-srv01
> PrimÃ¤res DNS-Suffix . . . . . . . : tm-consulting.de
> Knotentyp . . . . . . . . . . . . : Broadcastadapter
> IP-Routing aktiviert. . . . . . . : Nein
> WINS-Proxy aktiviert. . . . . . . : Nein
> DNS-Suffixsuchliste . . . . . . . : tm-consulting.de
>
>Ethernetadapter "LAN-Verbindung 2":
>
> Medienstatus. . . . . . . . . . . : Kabel nicht angeschlossen
> Beschreibung. . . . . . . . . . . : Intel(R) PRO/100 S Desktop
>Adapter
> Physikalische Adresse . . . . . . : 00-02-B3-88-AC-81
>
>Ethernetadapter "LAN-Verbindung":
>
> Verbindungsspezifisches DNS-Suffix:
> Beschreibung. . . . . . . . . . . : Intel(R) PRO/100 VE Network
>Connecti
>on
> Physikalische Adresse . . . . . . : 00-03-47-C2-BE-86
> DHCP-aktiviert. . . . . . . . . . : Nein
> IP-Adresse. . . . . . . . . . . . : 192.168.1.250
> Subnetzmaske. . . . . . . . . . . : 255.255.255.0
> Standardgateway . . . . . . . . . : 192.168.1.254
> DNS-Server. . . . . . . . . . . . : 192.168.1.250
>
>
>
>"Allen Anderson" <allen@sparkysystems.com> wrote in message
>news:mj53e0d5b7amg37daj6bth6o1291ccn006@4ax.com...
>> does this one site have any special firewalls or anything different
>> about its network configuration?
>>
>> Allen Anderson
>> http://www.glacialcomp...
>> mailto: allen@put my website base here.com
>>
>> On Tue, 29 Jun 2004 16:44:42 +0300, "Chadi Zwein" <zwein@hotmail.com_>
>> wrote:
>>
>> >This is a CAO scenario with lifetime management.
>> >The remote objects are created successfully!! (no exceptions).
>> >
>> >Following that, and in the function calling
>> >RemotingServices.GetLifetimeService on the remote object, a
>> >System.Net.Sockets.SocketException occurs, complaining that the server
>did
>> >not respond in a timely fashion or the connection to the server was
>reset...
>> >
>> >Server Stack Trace:
>> >at System.Net.Sockets.Socket.Connect(EndPoint remote EP)
>> >at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket()
>> >at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String
>> >machineAndPort)
>> >:
>> >:
>> >Exception Rethrown at [0]:
>> >at System.Runtime.Remoting.Proxies.RealProxy...
>> >:
>> >at System.Runtime.MarshalByRefObject.GetLifetimeService()
>> >at MyFunction()
>> >
>> >
>> >This error is occurring on exactly 1 testing site among 40 to 50 ones,
>but
>> >it always appears there. Nothing interesting in the event logs, and the
>IP
>> >configuration of both (Windows 2000 SP4) client and server machines is
>very
>> >basic. No firewalls involved.
>> >
>> >Any idea?
>> >
>>
>

Sunny

7/6/2004 2:29:00 PM

Actally, Windows shuts down the tcp/ip stack when there is no connected
adapter. Thats why loopback adapter helps

Sunny

In article <s76ke0dlf09b5tt7q9a0vbk202t598et2h@4ax.com>,
allen@sparkysystems.com says...
> I''ve run into problems with remoting where the line was disconnected
> too as some others have mentioned. There are also issues with
> multi-homed servers. I wrote an article that talks about multi-homed
> servers with CAO objects but I haven''t tried it with SAO objects as of
> yet. You can check it out here.
>
> http://www.glacialcomp.../ArticleDetail.aspx?artic...
>
> Beyond that, you might add a loopback adapter to the machines. I''ve
> found this seems to mitigate some problems when a primary network
> adapter is disconnected or disabled for one reason or another.
>
> Cheers,
> Allen Anderson
> http://www.glacialcomp...
> mailto: allen@put my website base here.com
>
> On Wed, 30 Jun 2004 17:42:39 +0300, "Chadi Zwein" <zwein@hotmail.com_>
> wrote:
>
> >No firewalls are invloved.
> >Here is the (very usual) IP configuration reported from the test site:
> >
> >======================================
> >CLIENT PC
> >======================================
> >
> >C:\Dokumente und Einstellungen\TM-Admin>ipconfig /all
> >
> >Windows 2000-IP-Konfiguration
> >
> > Hostname. . . . . . . . . . . . . : TM-PC1
> > Prim??res DNS-Suffix . . . . . . . : tm-consulting.de
> > Knotentyp . . . . . . . . . . . . : Broadcastadapter
> > IP-Routing aktiviert. . . . . . . : Nein
> > WINS-Proxy aktiviert. . . . . . . : Nein
> > DNS-Suffixsuchliste . . . . . . . : tm-consulting.de
> >
> >Ethernetadapter "LAN-Verbindung":
> >
> > Verbindungsspezifisches DNS-Suffix:
> > Beschreibung. . . . . . . . . . . : Intel(R) PRO/100 VE Network
> >Connecti
> >on
> > Physikalische Adresse . . . . . . : 00-03-47-DC-FE-91
> > DHCP-aktiviert. . . . . . . . . . : Nein
> > IP-Adresse. . . . . . . . . . . . : 192.168.1.10
> > Subnetzmaske. . . . . . . . . . . : 255.255.255.0
> > Standardgateway . . . . . . . . . : 192.168.1.254
> > DNS-Server. . . . . . . . . . . . : 192.168.1.250
> >
> >
> >
> >
> >======================================
> >SERVER PC
> >======================================
> >
> >C:\Dokumente und Einstellungen\tm-admin>ipconfig /all
> >
> >Windows 2000-IP-Konfiguration
> >
> > Hostname. . . . . . . . . . . . . : tmc-srv01
> > Prim??res DNS-Suffix . . . . . . . : tm-consulting.de
> > Knotentyp . . . . . . . . . . . . : Broadcastadapter
> > IP-Routing aktiviert. . . . . . . : Nein
> > WINS-Proxy aktiviert. . . . . . . : Nein
> > DNS-Suffixsuchliste . . . . . . . : tm-consulting.de
> >
> >Ethernetadapter "LAN-Verbindung 2":
> >
> > Medienstatus. . . . . . . . . . . : Kabel nicht angeschlossen
> > Beschreibung. . . . . . . . . . . : Intel(R) PRO/100 S Desktop
> >Adapter
> > Physikalische Adresse . . . . . . : 00-02-B3-88-AC-81
> >
> >Ethernetadapter "LAN-Verbindung":
> >
> > Verbindungsspezifisches DNS-Suffix:
> > Beschreibung. . . . . . . . . . . : Intel(R) PRO/100 VE Network
> >Connecti
> >on
> > Physikalische Adresse . . . . . . : 00-03-47-C2-BE-86
> > DHCP-aktiviert. . . . . . . . . . : Nein
> > IP-Adresse. . . . . . . . . . . . : 192.168.1.250
> > Subnetzmaske. . . . . . . . . . . : 255.255.255.0
> > Standardgateway . . . . . . . . . : 192.168.1.254
> > DNS-Server. . . . . . . . . . . . : 192.168.1.250
> >
> >
> >
> >"Allen Anderson" <allen@sparkysystems.com> wrote in message
> >news:mj53e0d5b7amg37daj6bth6o1291ccn006@4ax.com...
> >> does this one site have any special firewalls or anything different
> >> about its network configuration?
> >>
> >> Allen Anderson
> >> http://www.glacialcomp...
> >> mailto: allen@put my website base here.com
> >>
> >> On Tue, 29 Jun 2004 16:44:42 +0300, "Chadi Zwein" <zwein@hotmail.com_>
> >> wrote:
> >>
> >> >This is a CAO scenario with lifetime management.
> >> >The remote objects are created successfully!! (no exceptions).
> >> >
> >> >Following that, and in the function calling
> >> >RemotingServices.GetLifetimeService on the remote object, a
> >> >System.Net.Sockets.SocketException occurs, complaining that the server
> >did
> >> >not respond in a timely fashion or the connection to the server was
> >reset...
> >> >
> >> >Server Stack Trace:
> >> >at System.Net.Sockets.Socket.Connect(EndPoint remote EP)
> >> >at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket()
> >> >at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String
> >> >machineAndPort)
> >> >:
> >> >:
> >> >Exception Rethrown at [0]:
> >> >at System.Runtime.Remoting.Proxies.RealProxy...
> >> >:
> >> >at System.Runtime.MarshalByRefObject.GetLifetimeService()
> >> >at MyFunction()
> >> >
> >> >
> >> >This error is occurring on exactly 1 testing site among 40 to 50 ones,
> >but
> >> >it always appears there. Nothing interesting in the event logs, and the
> >IP
> >> >configuration of both (Windows 2000 SP4) client and server machines is
> >very
> >> >basic. No firewalls involved.
> >> >
> >> >Any idea?
> >> >
> >>
> >
>
>

microsoft.public.dotnet.framework.remoting

SocketException at GetLifetimeService

Chadi Zwein

Sunny

Allen Anderson

Chadi Zwein

Chadi Zwein

Chadi Zwein

Ken Kolda

Sunny

Chadi Zwein

Allen Anderson

Sunny

x Login to ForumsZone