DCOM Advise Error

I have an MFC executable which calls methods on a remote DCOM service.  This works fine.  When I try to set up bi-directional communications with either connection points or callbacks, the Advise method fails with error x80070776 - the object exporter specified was not found.  If I remove the linkage to other library dlls and leave just the exe, it works fine.  Security and all prep COM  calls appear fine.  I'm using standard oleautomation marshalling.
Any idea why one or more linked dlls would cause this error?
tcarterAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
jkrConnect With a Mentor Commented:
Found the following:

Receiving OR_INVALID_OXID (0x80070776)
When using COM creation APIs (such as CoCreateInstance, CoCreateInstanceEx,
or CoGetClassObject) to create remote objects (objects on other machines),
incorrectly configured network settings that otherwise appear to support
file or print sharing properly may cause Distributed COM to fail with the
distinguished error, OR_INVALID_OXID (0x80070776). This is typically not a
problem with COM, but this network configuration problem that is not exposed
by other networking operations that have fall-back behavior that differs
from COM over improperly configured protocols.
This failure can occur when a machine has been configured with TCP/IP as
well as another network transport, such as IPX/SPX, or NetBeui, but the
TCP/IP configuration is improperly configured. For example, it may be
configured to be dynamically assigned an IP address using DHCP, yet a DHCP
server may not be available, so it has no IP address. The solution is to
properly configure TCP/IP networking.

(http://groups.google.com/groups?hl=de&lr=&ie=UTF-8&oe=UTF8&selm=%23ozFXB6mBHA.2432%40tkmsftngp07)
0
 
nke2000Commented:
Are the dll's you are using set up for connection points?
0
 
tcarterAuthor Commented:
Only the dlls that utilize COM are set up for connection points.  Currently, the test code is embedded in CMainApp::InitInstance().  The other (non-system) dlls appear to load (implicit linkage) when I step over the line with the Advise().
0
 
tcarterAuthor Commented:
I tracked down the problem.  One of the dlls associated with my application is named "security.dll".  The connection point Advise loads some additional system dlls including "security.dll".  Finding this name already loaded for the process, system32\security.dll and several others do not get loaded.  Renaming my dll fixed it.
0
 
DanRollinsCommented:
hi tcarter,
I suggest that you post a message to Community Support indicating that you found the answer yourself and that you want a refund of your points but that the question deserves to be placed in the PAQ.  Please reference this Q#: Q_20318798.

Alternatively, you could give the points to jkr for that valuable bit of research that he did on your behalf.

-- Dan
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.