Fields #

Fields #

Fields #

Fields #

Fields #

Fields #

Fields #

Fields #

Fields #

Fields #

Fields #

Fields #

Fields #

Fields #

Fields #

Description

Message Queuing Triggers started successfully.

Message #

Message Queuing Triggers started successfully.

Description

Message Queuing Triggers service stopped.

Message #

Message Queuing Triggers service stopped.

Description

The parameters of the rule with the ID are now valid. The rule was evaluated successfully, and the action defined by it was executed.

Message #

The parameters of the rule %1 with the ID %2 are now valid. The rule was evaluated successfully, and the action defined by it was executed.

Description

The rules attached to the trigger with the ID are now valid. All the rules were evaluated successfully, and the actions defined by them were executed.

Message #

The rules attached to the trigger %1 with the ID %2 are now valid. All the rules were evaluated successfully, and the actions defined by them were executed.

Message #

The Triggers service has been set to run under the Network Service account, but this setting will take effect only after the Triggers service is restarted.  If you want the Triggers service to continue to run under the Local Service account (the default for the previous version of Triggers), modify the logon settings  for the Triggers service in Computer Management.

Message #

The change for the Triggers service to run under the Network Service account will not take effect as long as the "Allow service to interact with desktop" check box is selected.  To allow this change to take effect, clear the "Allow service to interact with desktop" check box on the Log On page of the Properties dialog box for Message Queuing Triggers in Computer Management and restart the service.

Description

Message Queuing Triggers initialization failed. Error.

Message #

Message Queuing Triggers initialization failed. Error %1: %2

Message #

Message Queuing Triggers failed to create an instance of the Triggers Transactional object. As a result, no transactional retrieval triggers can be invoked. Mqgentr.dll may not be registered or may not exist in the %SystemRoot%\System32 folder. Error %1: %2

Description

The trigger information cannot be retrieved from the trigger store in registry. At least one trigger is nonfunctional.

Message #

The trigger information cannot be retrieved from the trigger store in registry. At least one trigger is nonfunctional.

Description

The information for the attached rule cannot be retrieved from the trigger store for trigger (Trigger Name: ). The trigger is nonfunctional.

Message #

The information for the attached rule cannot be retrieved from the trigger store for trigger %1 (Trigger Name: %2). The trigger is nonfunctional.

Message #

Opening the queue %3 for peeking at or retrieving messages failed. Local users may not have been granted the Peek Message or Receive Message permission for this queue. The trigger %4 is nonfunctional. Error %1: %2

Message #

Opening an internal queue needed by the Triggers service failed. The account under which the Triggers service is running may not have permissions to open this queue, or the queue may have been deleted. To solve this problem, uninstall and reinstall the Triggers service. Error %1: %2

Message #

An instance of a rule handler for the rule %3 with the ID %4 was not created. The rule cannot be evaluated and executed. The MSMQTriggerObjects.MSMQRuleHandler class may not be registered, or your System folder does not contain mqtrig.dll. Error %1: %2

Message #

The action or a condition parameter for the rule %3 with the ID %4 was not parsed. The rule cannot be evaluated and executed. You can remove the rule entry from the Triggers registry and recreate it using local computer management. Error %1: %2

Description

The action defined by the rule with the ID was not invoked. The COM object may not be registered, or the executable file may not exist in your path. Error.

Message #

The action defined by the rule %3 with the ID %4 was not invoked. The COM object may not be registered, or the executable file may not exist in your path. Error %1: %2

Description

Rule evaluation or execution failed for the transactional trigger with the ID . A rule condition or action parameter may be invalid, or the COM object invoked may not be registered correctly. Error.

Message #

Rule evaluation or execution failed for the transactional trigger %3 with the ID %4. A rule condition or action parameter may be invalid, or the COM object invoked may not be registered correctly. Error %1: %2

Description

The queue was not found. It may have been deleted. The trigger associated with this queue is nonfunctional. Please use Computer Management to remove this trigger.

Message #

The queue %1 was not found. It may have been deleted. The trigger %2 associated with this queue is nonfunctional. Please use Computer Management to remove this trigger.

Description

At least one of the required dependencies was not found. Please verify that MSMQ Triggers resources are dependent on Message Queue resources.

Message #

At least one of the required dependencies was not found. Please verify that MSMQ Triggers resources are dependent on Message Queue resources.

Description

Unable to update EventLog information in registry for '%1'.

Message #

Unable to update EventLog information in registry for '%1'.

Description

The Triggers transactional component could not be registered in COM+. Error.

Message #

The Triggers transactional component could not be registered in COM+. Error %1: %2

Description

Retrieving messages from a queue located on a remote pre-Windows XP computer is not supported. All triggers associated with the queue are nonfunctional.

Message #

Retrieving messages from a queue located on a remote pre-Windows XP computer is not supported. All triggers associated with the queue %1 are nonfunctional.

Description

Message Queuing Triggers initialization failed to complete in the configured timeout..

Message #

Message Queuing Triggers initialization failed to complete in the configured timeout..