C# Interop Object Security Permissions Problem
From: John Cullen (JohnCullen_at_antispamcompany.com)
Date: 03/15/04
- Next message: godzooky: "problem wrapping an unmanaged class"
- Previous message: Jeff Ballance: "Help with marshalling buffer from Unmanaged to Managed code"
- Next in thread: Ying-Shen Yu[MSFT]: "RE: C# Interop Object Security Permissions Problem"
- Reply: Ying-Shen Yu[MSFT]: "RE: C# Interop Object Security Permissions Problem"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 15 Mar 2004 13:44:47 -0500
I seem to be running into an issue with creating an instance of a .net
object registered with COM interop from a legacy VC++6 MFC application.
My set up goes like this:
C++/MFC Windows Service spawns a process which in turn creates an instance
of my in-process (DLL) C# object through COM interop.
Everything works fine if I set up the service to log into an administrator
account... however if I have my service log in using the system account, I
run into issues creating the C# object.
My call to COleDispachDriver.CreateDispatch(<classname>) returns an "Invalid
Class String" CO_E_CLASSSTRING 0x800401F3L error when attempting to create
my C# object.
I have no issues with my legacy app creating "normal" ActiveX objects
written in VB6.
- Next message: godzooky: "problem wrapping an unmanaged class"
- Previous message: Jeff Ballance: "Help with marshalling buffer from Unmanaged to Managed code"
- Next in thread: Ying-Shen Yu[MSFT]: "RE: C# Interop Object Security Permissions Problem"
- Reply: Ying-Shen Yu[MSFT]: "RE: C# Interop Object Security Permissions Problem"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
