Re: TSP and COM, coCreateInstance failure

Chris,

> singleton from a TSP. I've run into this problem before, and I think
> it's security related.

So you did not actually solve the problem you described here.
I don't think that the "solution" you described here will solve
the problem. CoInitialize is the first thing you call before any
actual COM objects are involved, so how should changing any
COM security settings solve your CoInitialize problem?

Why didn't you follow my suggestions?


Best regards,

Matthias Moetje
-------------------------------------
TERASENS GmbH
Ackermannstraße 3
80797 München
-------------------------------------
Fon: +49 89 143370-0
Fax: +49 89 143370-22
e-mail: moetje at terasens dot de
www: www.terasens.de
-------------------------------------

<cmbardon@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:1128522522.692548.145600@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> I'm actually running into a similar situation, except that I have the
> added wrinkle of trying to invoke a COM object which is declared as a
> singleton from a TSP. I've run into this problem before, and I think
> it's security related.
>
> The solution to the problem was to change the identity of both the
> Service and the COM object to the same account (the service runs as
> Local System and the COM server as the launching user by default).
> Setting both of these identities to a common third account fixed my
> problem with CoInitialize, which was otherwise returning ACCESSDENIED.
> Of course, I'd rather not have to screw with the parameters on the
> Telephony Service-is there another solution that you guys have found?
>


.