>Here at EagleUSA I'm writing a out-of-process DCOM EXE server that will run on a NT4 server to simulate Record Locking in SQL Server 6.5
>
>The EXE registered fine on the NT machine and
>I can get the DCOM object to fire if I set the DCOMcnfg identity rights for that CLSID to "The launching user".
>But the problem is that if 5 people instantiate the DCOM object, then it generates 5 entries running on the NT server.(not good because there will be more than 500 users)
>ie: It causes multiple instances of the server to be launched on one computer.
>Microsoft solution "The most common approach is to create a dedicated Windows NT user account that serves as the security principal for distributed applications. Once you create a local or a domain account, you can configure the AppID by selecting This User and entering the user name and password. Once you configure your application to run using a specific user account, all objects activated from the AppID run in a single-server process."
>
>
>When we do that it creates the object (I think) but we cannot run any methods as we did before...
>
>Maybe the Service Control Manager cannot load the server process for some reason... We even gave the EXE (CLSID) administrator rights, and included SYSTEM user as indicated by Microsoft.
>
>Do you know what else can I try?
Does it have to be an exe? You might get lucky with a multi-threaded dll.