How to get around ActiveX requirement to Interact with Desktop

0

I have a Windows Service that attempts to create a COM object.

MOVEitAPI.clientObj mi = new clientObj();

When I run it as a Console Application it runs just fine. But when I run it as a Windows Service, it throws the error:

Retrieving the COM class factory for component with CLSID {99E6491E-539E-49B1-A85F-141C139655AF} failed due to the following error: 80070583 Class does not exist. (Exception ?from HRESULT: 0x80070583).

The only way I've found around this is to tick the "Allow service to interact with desktop" checkbox. With that box checked, it runs without error.

FYI, my service is 32bit.

Is there any way around this requirement, as I don't think the "Allow service to interact with desktop" option will be allowed in a production environment? I've read that its not as big an issue as it was pre-Vista because it is using Session 0. But I'd like an alternative.

c#
service
com
activex
asked on Stack Overflow Jun 13, 2013 by Clayton Hall

0 Answers

Nobody has answered this question yet.


User contributions licensed under CC BY-SA 3.0