Re: CoCreateInstance call failing with error E_NOINTERFACE

From:

"Alexander Nickolov" <agnickolov@mvps.org>

Newsgroups:

microsoft.public.vc.atl

Date:

Thu, 25 Jan 2007 11:13:44 -0800

Message-ID:

<#jlXvTLQHHA.2096@TK2MSFTNGP05.phx.gbl>

You explicitly stated this comes from a .NET remoting call.
..NET by default has nothing to do with STAs, so presumably
is uses MTA for COM Interop...

You may want to check this in the interop group:

microsoft.public.dotnet.framework.interop

Note I don't claim to understand your situation, so my guess
may be wrong and it's something else...

--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================

<catharticmomentusenet@yahoo.co.uk> wrote in message
news:1169735281.185353.294750@a75g2000cwd.googlegroups.com...

Thanks,

I've now proved to my own satisfaction that the caller is indeed
operating within an MTA, and this does indeed explain why I am seeing
marshalling problems. It does however beg the question "Why is the
caller in an MTA".

The caller is defined in an ATL DLL. The DLL has the line:

#define _ATL_APARTMENT_THREADED

in it's stdafx.h file, and I have confirmed that the registry lists the
class as being apartment threaded. Shouldn't this ensure that instances
are only created in an STA?