and orphaning it. I'm surprised you don't get a crash in the
point (e.g. after CoUninitialize)...
On Sep 30, 4:23 pm, "Alexander Nickolov" <agnicko...@mvps.org> wrote:
The problem is in your calls to CoInitializeEx and CoUninitialize.
Lose them (move them to the beginning and end of your thread
respectively) and you should be fine.
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnicko...@mvps.org
MVP VC FAQ:http://vcfaq.mvps.org
=====================================
"rtischer" <rtisc...@vacoxmail.com> wrote in message
news:1191018151.322761.249720@50g2000hsm.googlegroups.com...
I am getting this error when calling GetInterfaceFromGlobal in an
extension dll in my ATL server. My calling code looks like this:
HRESULT result = ::CoInitializeEx( NULL, COINIT_APARTMENTTHREADED );
CComPtr< IMyCallback > myCallback;
HRESULT result = globalInterfaceTable-
GetInterfaceFromGlobal( gitCookie,
IID_IAtlMyCallback, ( VOID ** )&myCallback );
CoUninitialize();
I know the code is good because I can put it directly in a spawned
worker thread and the GIT call returns S_OK. Also, since my
application code is well tested, I know the problem is not in the
thread switching or the extension dll loading or execution. This means
that either ATL GIT marshalling has a problem with PostThreadMessage
or extension dlls.
To test this out, I put the above code directly into the
PostThreadMessage handler and it too worked fine returning an S_OK.
But going one step further and calling a function in the extension dll
from the message handler, and the code fails returning E_NOINTERFACE.
Is there some peculiarity with marshalling that I don't know? I am
using the STA threading model. I'm an old hand at MFC and threads, but
am relatively new concerning ATL's need for marshalling across threads
in an ATL Server.- Hide quoted text -
- Show quoted text -
I moved the CoInitializeEx to the beginning and CoUninitialize to the
end of the thread but there was no change. The first call to
GetInterfaceFromGlobal succeeds, but the second call fails. Here is
the code with the initialization surrounding each call. Both calls
occur in the switched-to thread, but the second call occurs in the dll
code:
atlServerApp->PostThreadMessage( SOME_THREAD_HANDLER, wParam,
lParam );
...
void SomeWinAppThread::SomeThreadHandler( wParam, lParam )
{
HRESULT result = ::CoInitializeEx( NULL, COINIT_APARTMENTTHREADED );
CComPtr< IMyCallback > myCallback;
result = globalInterfaceTable->
GetInterfaceFromGlobal( gitCookie, IID_IAtlMyCallback,
( VOID ** )&myCallback ); <-- returns S_OK
CoUninitialize();
myExtDllHandle->MyExtDllMethod(...)
}
void MyExtDll::MyExtDllMethod(...)
{
HRESULT result = ::CoInitializeEx( NULL, COINIT_APARTMENTTHREADED );
CComPtr< IMyCallback > myCallback;
result = globalInterfaceTable->
GetInterfaceFromGlobal( gitCookie, IID_IAtlMyCallback,
( VOID ** )&myCallback ); <-- returns S_NOINTERFACE
CoUninitialize();
}
A colleague of mine suggested that the problem might be due to the
type of dll: extension dlls don't have their own message pump and STA
marshalling depends on that (I'm still reading up on this). This would
mean that I should switch to a regular dll which does have its own
message pump.