Re: Remote launch fails with E_ACCESSDENIED

As you would probably guess, CoGetClassObject also fails with
E_ACCESSDENIED.

If I replace my EXE with a copy of Notepad.exe, it also fails to launch
that.

Paul

"Paul Baker [MVP, Windows Desktop Experience]"
<paulrichardbaker@xxxxxxxxxxxxxxxx> wrote in message news:...
Gerry,

Thanks. That script works (Agent Version 7.0.6000.381).

I am not sure what details of my DCOM server are relevant. I will offer
some further details and maybe you have specific questions?

These are 32-bit systems and 32-bit Win32 processes and the server is out
of process. It has a user interface, but can also function through a
command line interface or DCOM server in a non-interactive window station.
I have recently moved some interactive functions from the server to the
client to facilitate running the server non-interactively without loss of
functionality. DCOM does not even launch the process, so I won't go into
the details of classes, interfaces, etc. at this point.

Paul

"Gerry Hickman" <gerry666uk@xxxxxxxxxxxxxxxx> wrote in message
news:OyPGhnXqIHA.4876@xxxxxxxxxxxxxxxxxxxxxxx
Hi Paul,

Before going any further, can you try running this simple code from the
client - look out for word wrap!

// TestDCOM.js
// Get the Agent Version
var strCmp = "YourServer";
var oAgentInfo = new ActiveXObject("Microsoft.Update.AgentInfo", strCmp);
var strVersion = oAgentInfo.GetInfo("ProductVersionString");
WScript.Echo("Agent Version " + strVersion);

If this works, it means both computers are configured for DCOM and
remoting and points to a problem specific to the object you are trying to
launch - in that case we'd need full details of the object.

Paul Baker [MVP, Windows Desktop Experience] wrote:
CoCreateInstance with a remote server name is returning E_ACCESSDENIED
before it even launches the remote server process. The client is Windows
XP SP2 and the server is Windows Server 2003. I am not calling
CoInitializeSecurity. The user is an administrator on both client and
server and the DCOM configuration and security settings are default, as
far as I know, and nothing looks wrong.

It works if I configure the AppID on both the client and server to run
as the "interactive user" (use DCOMCNFG) and the user is logged on to
the client and server console sessions. However, I get E_ACCESSDENIED if
I configure the AppID on both the client and server to run as "the
launching user", which is what I want (to avoid having to logon to the
console session or expose it to an interactive user).

Can anyone offer a suggestion on how to troubleshoot this?

Thanks,

Paul


--
Gerry Hickman (London UK)




.

Relevant Pages

  • Re: Remote DCOM on WinCE 6.0
    ... as in the client case. ... allowing the selected user name to start the server or, at least, access the ... You have to make sure that your code to actually create the remote ... Once you have all of that, run your DCOM client application in the ...
    (microsoft.public.windowsce.embedded)
  • Re: DCOM security in Windows Server 2003 SP1
    ... it's unfortunate that they chose a different name for it in the server edition if it's indeed the same thing. ... DCOM by one account or set COAUTHINFO in COSERVERINFO in CoCreateInstanceEx) with special activation privilege, for example, a domain account in the newly created build-in group "Distributed DCOM user", and switch back to the identity that runs the client program after the activation? ... like to grand remote activation permission to "Everyone" in the computerwide restrictions or DCOM limits whatever it is called, just because our client program fails. ...
    (microsoft.public.win32.programmer.ole)
  • Re: Remote DCOM on WinCE 6.0
    ... Now we're focussing on loading the server ... as in the client case. ... applet's Network ID tab to be a user name and password that the remote ... Once you have all of that, run your DCOM client application in the ...
    (microsoft.public.windowsce.embedded)
  • Re: Remote DCOM on WinCE 6.0
    ... In fact, the WinCE device will run the server, not the client. ... You have to make sure that your code to actually create the remote object ... Once you have all of that, run your DCOM client application in the debugger ...
    (microsoft.public.windowsce.embedded)
  • Re: COM question
    ... A DLL-based server with a custom interface *not* involving any weird ... This server will run on Windows CE 3 on this device and can be ... A client for above server compiled for Windows XP and connecting to the ... The CE device has the DCOM flag in the registry ...
    (microsoft.public.windowsce.platbuilder)