I Cannot See My Triggers Application on the Desktop, Although I See in Task Manager That the Application Is Running
Applies To: Windows Server 2008
Describes a specific problem with Message Queuing triggers. Includes step-by-step instructions for fixing the problem.
This problem typically occurs when you have configured a trigger to invoke an executable file that interacts with the desktop (such as notepad for example). When the trigger fires and invokes the executable file, you can see that the application is running in Task Manager but you cannot see the application running on your desktop as you would expect.
The Triggers service runs under the security context of the Network Service account by default. The Network Service account does not have permissions to interact with the desktop and so any executables that are invoked from the context of the Network Service account will not be visible on the desktop.
Follow these steps to configure the Triggers service to run as an account that has permission to interact with the desktop.
To configure the Triggers service to run as an account that has permissions to interact with the desktop.
Click Start, point to Programs, point to Administrative Tools, and then click Services.
In Services, scroll down the list of services to locate the Message Queuing Triggers service and double-click the Message Queuing Triggers service to display the service Properties dialog box.
Click the Log On tab.
Under Log on as select Local System account and enable the option to Allow service to interact with desktop or else select This account and enter an account name and associated password for an account that has permssion to interact with the desktop.
Restart the Message Queuing Triggers service.
After following the steps above, send a message to a queue monitored by a trigger which invokes an executable file that interacts with the desktop. The application invoked by the trigger should be visible on the desktop.