I have a COM+ application, which acts as a remoting server.  The .NET
assembly contains two COM visible objects - one is trigger by a service
to load a config file and start listening for remoting clients, the
other is used in remoting calls (there is another object which is the
actual remoting component because it seems a class cannot be a remoted
object and serviced component).

For installation, I use regasm /codebase, then gacutil to register the
.NET assembly, then regsvcs to add the components to the COM+
application (it's an existing application).

On one server, this is enough, and clients can create and make use of
the remoted object.  On another server (both are Windows 2003, no SP),
the remoting configuration object reports a successful start, but
clients are unable to use the remoted object.  Instead an exception is
thrown indicating that my assembly or one of its dependencies was not found.

The fact that I have used regasm /codebase _or_ GACed the assembly and
all of its dependencies should mean there won't be a problem.  I added
the folder storing the assembly and dependencies to the system path -
still no joy.  In desperation I put the assembly and dependencies into
the Windows\System32 folder - suddenly it started working.

I have checked and double checked that all file versions match between
the two servers and all clients.  I removed the application files and
configuration from both servers and started from scratch, one step at a
time, copying exactly what I did on both machines.  Still the same
situation - on one server the application will not work unless all of
the .NET files are in Windows\System32!

I don't understand what's going on.  Please can someone help!

Thank you
Ian