Ok, I am at my wits end and I need some help. I have a Windows Service that
is written in c#. This service configures the .NET remoting service. We
have this service installed on 300+ computers and on FOUR of them, the
remoting configuration fails.
When checking the event log, we see the following error posted while the
service is trying to start:
Remoting Configuration Failed: Remoting configuration failed with the
exception System.Reflection.TargetInvocationException: Exception has been
thrown by the target of an invocation. --->
System.Net.Sockets.SocketException: An invalid argument was supplied
at
System.Runtime.Remoting.Channels.Tcp.TcpServerChannel.StartListening(Object
data)
at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel()
at System.Runtime.Remoting.Channels.Tcp.TcpServerChannel..ctor(IDictionary
properties, IServerChannelSinkProvider sinkProvider)
at System.Runtime.Remoting.Channels.Tcp.TcpChannel..ctor(IDictionary
properties, IClientChannelSinkProvider clientSinkProvider,
IServerChannelSinkProvider serverSinkProvider)
--- End of inner exception stack trace ---
The Configuration file looks like this:
<configuration>
<system.runtime.remoting>
<customErrors mode="Off" />
<application name="ALMSAdministrationServer">
<service>
<wellknown mode="Singleton"
type="ALMS.Remote.Objects.LicenseManager, DBAbstraction, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=d345c481361166d0"
objectUri="ALMS.Remote.Objects.LicenseManager" />
<wellknown mode="Singleton" type="ALMS.Remote.Objects.DBAdmin,
DBAbstraction, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=d345c481361166d0" objectUri="ALMS.Remote.Objects.DBAdmin"
/>
<wellknown mode="Singleton" type="ALMS.Remote.Objects.DBStudent,
DBAbstraction, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=d345c481361166d0" objectUri="ALMS.Remote.Objects.DBStudent"
/>
<wellknown mode="Singleton" type="ALMS.Remote.Objects.DBCourse,
DBAbstraction, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=d345c481361166d0" objectUri="ALMS.Remote.Objects.DBCourse"
/>
</service>
<lifetime leaseTime="1D" />
<channels>
<channel ref="tcp" port="7000" displayName="ALMSAdministrationServer tcp
channel">
<serverProviders>
<formatter ref="binary" typeFilterLevel="Full" />
</serverProviders>
</channel>
</channels>
<customErrors mode="Off" />
</application>
</system.runtime.remoting>
</configuration>
The call that fails in the code is:
RemotingConfiguration.Configure("configfile");
I have googled all over for this error and can't seem to find anything
like it. The closest I have come is when that port is already in use, but
that gives a different System.Net.Sockets.SocketException.
If anybody out there knows anything that might help, I would be 100%
appreciative.
Here are the things we have already tried
1) Applying the .NET 1.1 Service Pack 1
2) Checking all security permissions, everywhere
3) In the .NET Framework 1.1 Configuration applet, making sure that the
"delayLoadAsClientChannel" option was set to true for both HTTP and tcp in
the Remoting Services Properties
4) Checked the GAC to make sure that the Remoting DLL was there, and the
right version, and only one of them
5) Removing .NET and reinstalling it.
The sad thing is that there doesn't appear to be any corralation between
the hardware/software configurations. One of the users is running Windows
XP Pro Sp2, One is running XP Home SP1, and one is running Windows Server
2003. We have tried and tried and tried to duplicate this problem to no
extent, and we are out of ideas. We need help!
