Re: TSP and COM, coCreateInstance failure

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?

.