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. ATL / WTL / STL
  4. ATL web server and smart pointers

ATL web server and smart pointers

Scheduled Pinned Locked Moved ATL / WTL / STL
c++comsysadminhelpquestion
3 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.
  • D Offline
    D Offline
    De Nardis Andrea
    wrote on last edited by
    #1

    Hi all, I need to access a COM object from my ATL web service. The COM object is propely registered in the target machine and can be freely accessed from a VB client. I am using smart pointer in order to create an instance. When I invoke _com_ptr_t::CreateIntance I get as HRESULT "class not registered". What was wrong? Please help me!!! best Regards, Andrea :)

    I 1 Reply Last reply
    0
    • D De Nardis Andrea

      Hi all, I need to access a COM object from my ATL web service. The COM object is propely registered in the target machine and can be freely accessed from a VB client. I am using smart pointer in order to create an instance. When I invoke _com_ptr_t::CreateIntance I get as HRESULT "class not registered". What was wrong? Please help me!!! best Regards, Andrea :)

      I Offline
      I Offline
      Igor Vigdorchik
      wrote on last edited by
      #2

      Your client computer does not know anything about your COM object, mainly where it is located (this info is taken from the registry). I have not done it for a long time, but I recall that the correct way to create a component remotely is by using CoCreateInstanceEx(). Look up the MSDN, it should have enough info.

      D 1 Reply Last reply
      0
      • I Igor Vigdorchik

        Your client computer does not know anything about your COM object, mainly where it is located (this info is taken from the registry). I have not done it for a long time, but I recall that the correct way to create a component remotely is by using CoCreateInstanceEx(). Look up the MSDN, it should have enough info.

        D Offline
        D Offline
        De Nardis Andrea
        wrote on last edited by
        #3

        Thanx a lot, I found the problem, and this could be interesting for you, too. My COM dll server was properly registered in a substituted volume (V:) that does not exists at Windows startup. For some reason this prevents the interface from being accessed in inetinfo processo. Placing my COM dll (ATL COM inproc server, by the way) in %windir%\system32 all works well. Thanks a lot for your help. Best Regards, Andrea ;)

        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