This topic discusses the most common problems encountered with the Message Queuing Triggers service.

What problem are you having?

The Message Queuing Triggers service fails to start.
  • Cause:  The Message Queuing Triggers service has been configured to run under a domain user account without proper administrator permissions.

  • Solution:  Configure the Message Queuing Triggers service to run under the default Network Service account, which has sufficient permissions to run the Message Queuing Triggers service. Alternatively, grant yourself the necessary permissions. The Triggers service must run under an account with administrator permissions.

  • Cause:  The Message Queuing Triggers service has failed. In-process Component Object Model (COM) components that are invoked can sometimes fail and thereby cause the Message Queuing Triggers service to fail.

  • Solution:  Rectify the condition that causes the COM component to fail, and then restart the Message Queuing Triggers service.

A trigger is defined, but it does not appear to be firing.
  • Cause:  The trigger is currently disabled.

  • Solution:  Verify that the trigger has been enabled.

  • Cause:  The account under which the Message Queuing Triggers service is running has not been granted the Peek Message permission for the monitored queue. Or, if the message processing type of the trigger is retrieval or transactional retrieval, the account has not been granted the Receive Message permission for that queue.

  • Solution:  Change the permissions for the queues, and then restart the Message Queuing Triggers service.

  • Cause:  The Message Queuing Triggers service is not running.

  • Solution:  Verify that this service has been started.

  • Cause:  The Message Queuing Triggers service has been paused.

  • Solution:  Verify that this service is not in a paused state. To do this, open Computer Management, click Services and Applications, and then click Services. In the details pane, if the status for the Message Queuing Triggers service is set to Paused, right-click the service, and then click Resume.

  • Cause:  The trigger conditions are not all satisfied. If any trigger condition evaluates as false, the trigger will not fire.

  • Solution:  Verify that all conditions of the rule are true.

  • Cause:  The Message Queuing Triggers service cannot be initialized when running under a non-administrator account.

  • Solution:  By default, the Message Queuing Triggers service runs under the Network Service account. If you have changed this default, ensure that the account you have specified has administrator permissions.

The processing of messages by the Message Queuing Triggers service slows disproportionately as more messages arrive at a monitored queue.
  • Cause:  This is normal when the Message Queuing Triggers service runs under heavy loads. It occurs because the maximum number of threads is reached.

  • Solution:  You can accelerate the processing of messages by increasing the maximum number of allowable threads. To do this, open Computer Management, click Services and Applications, click Message Queuing, right-click Triggers, and then click Properties. Increase the maximum number of threads in Max number of threads.

I cannot see my triggers application on the desktop, although I see in Task Manager that the application is running.
  • Cause:  The Message Queuing Triggers service runs by default under the Network Service account; interaction with the desktop functionality is only available for the Local System account.

  • Solution:  Configure the Triggers service to run under the Local System account and enable it to interact with the desktop. To do this, in Computer Management, click Services, and in the details pane, double-click Message Queuing Triggers. Click the Log On tab, click Local System, and then select the Allow service to interact with desktop check box.

  • Troubleshooting Administration Problems
  • Troubleshooting by Using End-to-End Tracing