Error When Interop'ing to COM+ Managed Object with Library Activation

[Matt Dinovo]

I have a remoting server that is on the same local box as a COM+ managed
object with Library Activation. When I try to activate the object from the
remoted assembly, I get the following error: "The specified activation could
not occur in the client context as specified." The security context of the
service application that is activating the object has the proper
credentials. It's been years since I've had to deal with COM+ and I'm a bit
rusty. Is there some magic that I have to perform to get this interop to
work?

Thanks,

Matt Dinovo
dinovom [at] gmail.com

[Matt Dinovo]

I think I solved my issue. The issue was not that the package was set for
Library activation. The issue was the enforcement of access checks, coupled
with the security level. I ended up having to create another COM stub object
that I could place in a COM+ package that would broker the communication
between the .NET service and the library package. Not sure exactly why this
works, but I'm not complaining...

Thanks,

Matt
"Matt Dinovo" <dinovom@[NOSPAM].gmail.com> wrote in message
news:ep**************@TK2MSFTNGP09.phx.gbl...

I have a remoting server that is on the same local box as a COM+ managed
object with Library Activation. When I try to activate the object from the
remoted assembly, I get the following error: "The specified activation
could not occur in the client context as specified." The security context
of the service application that is activating the object has the proper
credentials. It's been years since I've had to deal with COM+ and I'm a bit
rusty. Is there some magic that I have to perform to get this interop to
work?

Thanks,

Matt Dinovo
dinovom [at] gmail.com