Interface not registered (CoCreateInstanceEx)

[Guest_imported]

I have a "DCOM-Server" on WinNT und try to create/use this Components in a application in WinCE [out-of-process]. With CoCreateInstanceEx in WinCE I can start the DCOM-Server on WinNT. But how can I use the components in the WinCE-Application (executing Methods from the Components)?! In the Task-Manager of WinNT I see the DCOM-Server starting!

I can execute CoCreateInstanceEx only with mlti_qi.pIID=&IID_IUnknown. If I set mlti_qi.pIID=&IID_IExample then the Return-Pointer to my Object is NULL?? My Application doesn't know IID_IExample... but I am sure that IID_IExample is registered on the WinNT-Registry!

What do I have to do?

Thank you very much:

 

[Guest_imported]

In WinCE I can't use the Proxy-Stub-DLL built in WinNT. This could be the problem (so I miss the Standard-Marshaller). Is there a way build the Proxy-Stub-DLL for WinCE?!

 

[kannanl2k]

Hi,
i also have a "DCOM-Server" on WinNT und try to create/use this Components in a application in WinCE [out-of-process]. WHen i use CoCreateInstanceEx to get the interface pointer of the server, It returns the error E_ACCESSDENIED. Well, i gave permissions for launch as well as access for everyone for that component. I registered the Server in WInCE and specifying the Remote Machine Name also. If anybody has some any idea, it will be really helpful. it is very urgent..

thanks in advance,
kannan

 

[Cagliostro]

This means your interface is not regisetrend in registry under key:
\HKEY_CLASSES_ROOT\Interface
There is also an other key for class ID's what must eb registered:
\HKEY_CLASSES_ROOT\CLSID

Ion Filipski

ICQ: 95034075
AIM: IonFilipski
filipski@excite.com

 

[kannanl2k]

Yes, In WinCE you can't use the Proxy-Stub-DLL built in WinNT. But there is a way around.Create a empty project in embedded Visual c++. Add the file dlldata.c and all the neccessary _i.c and _p.c files for that server into that project. And from that project, u can generate a proxy -stub dll which can be used in WinCE.
The reason for this is the proxy stub dll generated in WinNT is dependent of Kernel32.dll, which is not available in WinCE. So you have to create a proxy stub dll which is dependent core.dll ( WInCE specific)

 

[kannanl2k]

I m able to connect to the WinNT DCOM server, using the WInCE Proxy Stub DLL from the Client(winCE ). It works when the Authentication level is RPC_C_AUTHN_LEVEL_NONE in both the client side and the server side. If the authentical level is RPC_C_AUTHN_LEVEL_CONNECT, then it throws "Security Context Invalid" error. Error Code : 0x800706D5. plz anyone can help ??

Thanks,
Kannan