Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. COM
  4. "interface not compatible"

"interface not compatible"

Scheduled Pinned Locked Moved COM
questionsysadminhelp
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • P Offline
    P Offline
    pelos
    wrote on last edited by
    #1

    hi, what is the meaning of the error "interface not compatible" returned by HRESULT? In the client I include the server header file which contains the definition of the remote interface. So, it must be the same interface. Thanks!!!

    L 1 Reply Last reply
    0
    • P pelos

      hi, what is the meaning of the error "interface not compatible" returned by HRESULT? In the client I include the server header file which contains the definition of the remote interface. So, it must be the same interface. Thanks!!!

      L Offline
      L Offline
      Lost User
      wrote on last edited by
      #2

      hello, i think i know what is the problem: I also need a proxy/stub DLL. So, I need to register the proxy/stub DLL on both the client and the server computers. To regisrer the DLL on the server i have done: nmake -f Projectnameps.mk where projectname is the name of my project. This command has built several files, included the Projectname.dll file. Now the problem is that i dont know very well how to register the DLL on the client. I have tried two differents things: 1.- Set up the remote activation using progammatic changes to the client (call CoCreateInstanceEx()instead CoCreateInstance()(),...).But it doesn't run. 2.- Follow the instructions of this article http://www.apostate.com/programming/reg-atl-dcom.html but i dont understand very well the last step: "Use DCOMCNFG to change the execution location of your server from Run application on this computer to Run application on the following computer", and this way to register the DLL sounds a bit rare, doesn´t it?. I am confused... Can you help me? thanks.

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups