Re: Automation from NT Service Launches 2nd process

Hope someone can help point me in the right direction. This is a bit
complex to explain, but I will try to simplify.

The Scenario:

NT Service that uses an IScriptSite interface to invoke a vbscript.
Service is running as LocalSystem, Interact with Desktop is enabled.

Contents of vbscript is:

Set myApp=CreateObject("myapplication.display")

myApp.ShowClientGUI()

MyApplication is running on the users desktop. It is an ATL/MFC
application that has been automation enabled primarily by the
methodology described in the following article with updates for VS.NET
2003:
http://www.codeguru.com/Cpp/COM-Tech/atl/atl/article.php/c55/

I have defined my Application Class as
CComObjectGlobal<MyClientApp> theApp;

It exposes the following methods:

STDMETHOD(ShowClientGUI)(void);
STDMETHOD(HideClientGUI)(void);
STDMETHOD(GetClientUIBrowser)(IDispatch* *lInterface);

Have Declared it's own class factory:

DECLARE_CLASSFACTORY_EX(CMyClientAppCF)

Which provides a CreateInstance() method

That performs the following:
g_theAppPtr->QueryInterface(riid,ppvObj);

The Problem:
This works great if the vbscript is run as a user on the desktop. It
recognizes that MyApplication is already running and invokes the class
factory to call createinstance which returns the appropriate interface.
However, when this is run from the service, it doesn't appear to
recognize that MyApplication is already running on the desktop, creates
a new process and fails in the class factory CreateInstance() because
the global MyApplication pointer (assigned in the original process
:InitInstance() is now invalid.

The Goal:
Ultimate goal is to have the vbscript running from the service, call
the methods in the object that is running on the user desktop to
perform UI updates.

Has anyone seen this before or tried to implement something similar?

Thanks