Re: CoCreateInstance returns COR_E_MEMBERACCESS error
Just a thought (since this is on the fringe of my experience), this looks
like one of those new HRESULTs that Microsoft has defined in order to map to
new exceptions that are generated by the .NET assembly for which there was
no previous COM equivalent. In this case COR_E_MEMBERACCESS is mapped to
AccessException.
The big difference which probably is playing a role here, is the fact that
VS 2005 uses .NET 2.0, and I'm suspicious some enhanced security features
may be responsible. Obviously, you should confirm the .NET Framework 2.0 is
present on the target machine.
Does MyClass have a constructor? Try placing a breakpoint there and see if
it gets executed. I'm wondering if you might be able to trace to the thrown
exception.
If you don't get much of a response here, you might want to try the
microsoft.public.dotnet.framework.interop newsgroup.
Brian
"prose" <prosen@inovasolutions.com> wrote in message
news:1182202427.065931.47600@p77g2000hsh.googlegroups.com...
The return value from CoCreateInstance is COR_E_MEMBERACCESS. I've
looked around the 'net and on MSDN and can't find any info on this.
How would I approach figuring out what is causing that return value?
In other words, does that error code give me some kind of clue about
what to change?
---- Background: -----
The COM DLL is a .NET C-sharp program that begins:
namespace MyNamespace
{
[Guid("822F83B3-644F-4c59-AA2A-7257D0ABE301")]
public interface IManagedInterface
{
bool Configure(string iniPath);
bool Connect();
bool Disconnect();
string GetUpdate();
}
[Guid("0D75D411-AD2F-419c-94EE-91A251ABC41D")]
public class MyClass : IManagedInterface
{
etc....
The calling code is:
IManagedInterface* pInterface = NULL;
HRESULT hr = CoCreateInstance(CLSID_MyClass,
NULL, CLSCTX_INPROC_SERVER,
IID_IManagedInterface,
reinterpret_cast<void**>(&pInterface ));
I have registered the resulting DLL with REGASM.
The exact same code worked in an earlier release of our product. The
only difference I can see is that the older version was compiled with
MSVC 7.1, and the current release is using MSVC 8.0.
I can drop the older DLL over the newer one and my app starts working.
As near as I can tell, the code is identical in the two versions and
they were registered the same way.
Thanks for any clues!