SYMPTOMS
Calling the AtlAdvise() function to setup a connection
point might return one of the following error numbers:
0x80004002 (E_NOINTERFACE or "No such interface supported")
0x80040200
(CONNECT_E_NOCONNECTION)
0x80040202
(CONNECT_E_CANNOTCONNECT)
RESOLUTION
E_NOINTERFACE Error
For the E_NOINTERFACE error, verify that the source or server
supports the IconnectionPointContainer interface. In ATL, this means that the
source object should derive from the IConnectionPointContainerImpl class and
that IConnectionPointContainer needs to be in the COM map, as in the following
example:
Sample Code
class ATL_NO_VTABLE CMySource :
public IConnectionPointContainerImpl<CMySource>
...
BEGIN_COM_MAP(CMySource)
...
COM_INTERFACE_ENTRY_IMPL(IConnectionPointContainer)
END_COM_MAP()
CONNECT_E_NOCONNECTION Error
For the CONNECT_E_NOCONNECTION error, verify that there is a
connection point entry for the globally unique identifier (GUID) of the event
interface in the connection point map, as in the following example:
Sample Code
BEGIN_CONNECTION_POINT_MAP(CMySource)
CONNECTION_POINT_ENTRY(DIID__MySourceEvents)
END_CONNECTION_POINT_MAP()
CONNECT_E_CANNOTCONNECT Error
For the CONNECT_E_CANNOTCONNECT error, verify that the event
interface is in the sink, or client, COM map, as in the following example:
BEGIN_COM_MAP(CDispSink)
COM_INTERFACE_ENTRY(IDispatch)
COM_INTERFACE_ENTRY_IID(DIID__MySourceEvents, IDispatch)
END_COM_MAP()
Another cause of failure might be that the event interface is a custom
interface and the source, or server, is out of process (an .exe file). You need
to install a marshaler for the custom interface for QueryInterface() to work
across process boundaries.
If all the methods of the event interface
pass automation-compatible types (they are VARIANT-compatible), you can set an
attribute of "oleautomation" in the source .idl file. When an ATL server is
registered, its type library is also registered. This sets up the marshaler for
this interface to be the universal marshaler (in OleAut32.dll).
If
the event interface passes non-automation-compatible types, then a proxy DLL
needs to be built and registered. The ATL Project Wizard creates a proxy
makefile in your project directory with the name <Project>.mk. You can
run NMake.exe on this .mk file to build the proxy DLL.