Re: Remote DCOM on WinCE 6.0
- From: "Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT com>
- Date: Mon, 29 Sep 2008 09:34:39 -0700
It's not supported. Don't you see that in the OS documentation? I seem to
remember it being all over the place. DCOM is supported, in the sense that
you can use out-of-process COM on Windows CE 6.0, if you build the right
pieces into the OS, but Remote DCOM is not.
Paul T.
"MilanvdM" <MilanvdM@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F1DADEA9-C8B1-4972-A0D2-54B3A2B4A34E@xxxxxxxxxxxxxxxx
The company I work for is implementing control of a piece of equipment on
an
ARM-based board running Windows CE 6.0. The board is to be controlled from
a
PC running XP Embedded. We will use DCOM. We applied the DCOM .msi to
Platform Builder to incorporate DCOM remoting in CE 6.0. The network is
closed, so we do not have to be worried about security issues.
We've been struggling for two weeks now to get DCOM remoting to work, but
it
does not yet. We've created a demo application on WinCE that creates a COM
server inproc, but outproc just does not work. Below, you see some
logging.
Whatever we change, we just keep getting an 80070005 upon calling
CoCreate().
My question is whether there is some kind of readme on how to set up
remote
DCOM in CE 6.0 ?
I understand from blogs and discussion groups there's a lot to set up to
get
remote DCOM to work in CE6.0. In microsoft.public.windowsce.embedded, on
8th
July this year, John Spaith stated there's an example available for CE5.0
to
add numbers across distributed machines. Is such an example available for
CE
6.0 too?
Any help will be greatly appreciated.
Logging of our current demo application:
4294937025 PID:2660006 TID:2670006 ********************************
4294937026 PID:2660006 TID:2670006 CoInitSecurity: 0
4294937177 PID:2660006 TID:2670006 OSAXST1: >>> Loading Module
'secur32.dll'
(0x83BAA180) at address 0x402C0000-0x402CA000 in Process 'Test4CE.exe'
(0x83AD139C)
4294937274 PID:400002 TID:2700006 OSAXST1: >>> Loading Module
'rpcltccm.dll'
(0x83C3321C) at address 0x405A0000-0x405A8000 in Process 'NK.EXE'
(0x81038AA0)
PB Debugger Loaded symbols for 'N:\...<cut\>...\RPCLTCCM.DLL'
4294937275 PID:2de0002 TID:2700006 OSAXST1: >>> Loading Module
'rpcltccm.dll' (0x83C3321C) at address 0x405A0000-0x405A8000 in Process
'servicesd.exe' (0x83AF8000)
4294937284 PID:2de0002 TID:2700006 SECUR32: Locating package 'NTLM' ...
4294937284 PID:2de0002 TID:2700006 found (0x10023770).
4294937361 PID:2de0002 TID:2700006 02de0002.02700006>
4294937361 PID:2de0002 TID:2700006 Cairole:
4294937362 PID:2de0002 TID:2700006 DCOMSS: Failed on
RpcBindingSetAuthInfoEx
for remote machine binding
4294937391 PID:2de0002 TID:28c0006 02de0002.028c0006>
4294937392 PID:2de0002 TID:28c0006 Cairole:
4294937392 PID:2de0002 TID:28c0006 DCOMSS: Call disallowed by
CkIfCallAllowed
4294937397 PID:2de0002 TID:2700006 02de0002.02700006>
4294937397 PID:2de0002 TID:2700006 Cairole:
4294937398 PID:2de0002 TID:2700006 DCOMSS:Error CallRemoteSCM (global)
successful connect - failure in remote activation
4294937404 PID:2660006 TID:2670006 CoCreate: 80070005
4294937450 PID:2660006 TID:2670006 OSAXST1: <<< Unloading Module
'ole32.dll'
(0x83B74870) at address 0x40330000-0x4043B000 in Process 'Test4CE.exe'
(0x83AD139C)
.
- Follow-Ups:
- Re: Remote DCOM on WinCE 6.0
- From: MilanvdM
- Re: Remote DCOM on WinCE 6.0
- References:
- Remote DCOM on WinCE 6.0
- From: MilanvdM
- Remote DCOM on WinCE 6.0
- Prev by Date: Re: Basic question on Windows Embedded
- Next by Date: Re: Remote DCOM on WinCE 6.0
- Previous by thread: Remote DCOM on WinCE 6.0
- Next by thread: Re: Remote DCOM on WinCE 6.0
- Index(es):
Relevant Pages
|
Loading
