Were you trying to converse with the server's local autmgr32 service with a (server local) DCOM? Is this where you got the access denied?


According to the docs; "remote com" requires AutMgr32 to be running; however, it is not a service, it's an application. I followed the docs to "run it as a service" but on NT / TS it does not work.

So then I went to DCOM to try to get that to work; but only the 1st of my 'classes' (located w/in my .exe) is seen by dcomcnfg.

On the client side; when running DCOM; I get access denied when I try to createobjectex() my com (on the server)... I've tweaked with settings; but can't seem to find the right combo of settings to get it all to work.

I tried MTS; but that fails too under Terminal Server.

So; I guess it's just that TerminalServer isn't enough like NT to work.

I just want to have a COM object that runs on a server; and my apps talk to it. Remote COM (now "obsolete" re: MS) didn't work; requires AutMgr32 to be running on the server (while it wsa running; this worked nicely) DCOM, as I understand it; doesn't require anything extra to be running on teh server. MTS should have worked; but it didn't.