I have a interesting problem and thought this would the right forum for
it.

Background:
We have created a series of new generation middleware components using
.NET/C#.  These components are managed DLLs hosted in a WIndows
Services and .NET Remoting is used for alll client comm. to these
components.  As documented in several books, using Windows Service as
host provides us with the equivalent "emulation" of a classic COM
Singleton local Server.

Now, these remoted managed singleton components connect to a classic
COM singleton server for all their data tracing needs (using COM
interop).  This works fine.  The nature of the singleton tracer server
is to provide our system with a single point for all data tracing.  So
client applications as well as other COM Componenets are free to
connect and use this tracer server.  This is all fine also.

Scenario:
Client application (managed OR unmanaged) connected to Classic COM
components as well as Remoted Managed .NET Components.  All of the
above may connect to the classic COM Tracer Server.

Problem:
The COM Libs/Runtime seems to create TWO instances of the *Singleton*
tracer Server!  one instance is shared by ALL connections made from
Windows Serivces while the other instance is shared by ALL coinnections
NOT made from Windows Services! (remember, Windows Service is only used
to host a managed DLL)

Tried:
Running the Windows Services as LocalSystem or LocalUser, but with the
same results...

Thanks for reading this far and please let me know if you need more
detail...

Regards,

Fadi