Event ID 2254 — Message Queuing Operation

Event ID 2254 — Message Queuing Operation

Updated: December 3, 2008

Applies To: Windows Server 2008 R2

Message Queuing operation provides message authentication, message encryption, dead-letter queues, security settings, and other basic features. If Message Queuing has problems with any of these features, proper Message Queuing operation may suffer.

Event Details

Product: Windows Operating System
ID: 2254
Source: MSMQ
Version: 6.1
Symbolic Name: EVENT_WARN_DEADLETTER_QUEUE_AUTHENTICATED
Message: The message could not be moved to deadletter queue %1. The deadletter queue is authenticated and the authenticity of the message could not be verified. The message will be moved to the system transactional dead letter queue.

This event is logged at most once per %2 seconds. To change this setting, set \HKLM\Software\Microsoft\MSMQ\Parameters\Event2254 registry value to desired time in seconds.

Resolve
Confirm that the message is properly signed or allow the dead-letter queue to receive nonauthenticated messages

The dead-letter queue that is mentioned in the error is authenticated, but the MSMQ Service could not confirm the authenticity of the message in the dead-letter queue. To resolve this issue, do one of the following:

  • Confirm that the computer that sent the message is properly signing its authenticated messages. For more information about signing messages, see Message Authentication (http://go.microsoft.com/fwlink/?LinkID=104732).
  • Allow the dead-letter queue to receive nonauthenticated messages.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority. If you want to modify permissions, you also must have the Set Properties permission on the specified queue.

Allow the dead-letter queue to receive nonauthenticated messages

To allow the dead-letter queue to receive nonauthenticated messages:

  1. Open the Computer Management snap-in. To open Computer Management, click Start. In the search box, type compmgmt.msc, and then press ENTER.
  2. In the console tree, expand Services and Applications, and then expand Message Queuing.
  3. Right-click the desired queue, and then click Properties.
  4. On the General tab, clear the Authenticated check box.

For more information about sending authenticated messages, see Message Authentication (http://go.microsoft.com/fwlink/?LinkId=104732).

Verify

Verify that the MSMQ Service is installed and running.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that the MSMQ Service is installed and running:

  1. Open the Services snap-in. To open Services, click Start. In the search box, type services.msc, and then press ENTER.
  2. Locate the Message Queuing service, and confirm that the value in the Status column is Started.

Related Management Information

Message Queuing Operation

Message Queuing

Related:

Event ID 2220 — Message Queuing Clustering

Event ID 2220 — Message Queuing Clustering

Updated: December 3, 2008

Applies To: Windows Server 2008 R2

Clustering makes it possible for Message Queuing to operate as one instance across multiple operating systems so that Message Queuing can fail-over from one computer to another and provide high availability.

Event Details

Product: Windows Operating System
ID: 2220
Source: MSMQ
Version: 6.1
Symbolic Name: EVENT_ERROR_MSMQ_CLUSTER_BIND_IP_NOT_EXIST
Message: <p>The IP address %1 specified in the \HKLM\Software\Microsoft\MSMQ\Parameters\%2 registry value is not a valid IP address for this computer.</p>

Resolve
Configure correct IP Address

The IP address is not configured properly in the registry.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To configure IP address:

Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.

  1. Open the Registry Editor. Click Start, in the search box type regedit, and then hit ENTER.
  2. Browse to the registry key specified in the event.
  3. Either remove the registry value or set it to the IP address suggested in the event.

Verify

You can use Failover Cluster Management to determine whether the Message Queuing cluster resource is online, or you can use the Cluster.exe tool to determine whether Windows Failover Clustering is installed and running.

Related Management Information

Message Queuing Clustering

Message Queuing

Related:

Event ID 2216 — Trigger Operation

Event ID 2216 — Trigger Operation

Updated: January 31, 2008

Applies To: Windows Server 2008

Message Queuing Triggers is a service that you can use to associate the arrival of each incoming message at a queue with a response that depends on the contents of the message. The response may invoke either a Component Object Model (COM) component or a stand-alone executable program. These components or programs can define business rules that can be invoked in response to such messages, without any additional programming. An issue with triggers operations can, depending on the issue, prevent the invocation of some or all business rules.

Event Details

Product: Windows Operating System
ID: 2216
Source: MSMQ
Version: 6.0
Symbolic Name: MSMQ_TRIGGER_RETRIEVE_DOWNLEVL_QUEUE_FAILED
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.

Resolve
Convert to a peeking trigger or recreate the queue on Windows XP or Windows Vista

Retrieving messages from a queue that is located on a remote pre-Windows XP computer is not supported. You can fix this issue by changing the trigger type and have an application or COM object retrieve the message from the queue or re-create the queue on a Windows XP or Windows Vista computer.

Note: A peeking trigger checks a message in the queue but the message is not deleted.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Convert the trigger to a peeking trigger

Change the trigger to a peeking trigger, and provide an application or COM object that will take care of retreiving the message from the queue. Use this option if your business logic for handling messages does not require a retrieval trigger.

Note: If there is nothing in your Message Queuing setup that retrieves messages from your queues, your Message Queuing performance will suffer. Consider using queue quotas and implementing a solution that consumes messages that have arrived in your queues. For more information, see article 899612 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkID=107359).

To change the trigger to a peeking trigger:

  1. Open the Computer Management snap-in. To open Computer Management, click Start. In the search box, type compmgmt.msc, and then press ENTER.
  2. In the console tree, expand Services and Applications, expand Message Queuing, expand Message Queuing Triggers, and then click Triggers. Your triggers are in the details pane. The Queue Path Name column includes the computer name.
  3. For each trigger that is associated with a queue on a pre-Windows XP computer, right-click the trigger, and then click Properties.
  4. In Message processing type, confirm that Peeking is selected. If Peeking is not currently selected, select that option, and then click OK.

Recreate the queue on Windows XP or Windows Vista

Recreate the queue with the attached trigger from the pre-Windows XP computer to a Windows XP or Windows Vista computer. Use this option if you need the trigger retrieval functionality and can use a Windows XP or Windows Vista computer to host the queue that is currently on the pre-Windows XP computer.

Note: Any applications that are currently sending messages to this queue must be altered to send to the new queue on the Windows XP or Windows Vista computer, or the messages must be forwarded from the pre-Windows XP queue to the new queue on the Windows XP or Windows Vista computer.

To recreate pre-Windows XP queues on Windows XP or Windows Vista:

  1. Create a new queue on the Windows XP or Windows Vista computer. To create a new queue, on the Windows XP or Windows Vista computer, click Start. In the search box, type compmgmt.msc, and then press ENTER.
  2. In the console tree, expand Services and Applications, and then expand Message Queuing.
  3. Right-click either Public Queues or Private Queues, point to New, and then click Private Queue (or Public Queue).
  4. Configure the properties of the new queue with the same properties as the pre-Windows XP queue from the event error.
  5. On the computer that has the original trigger, open the Computer Management snap-in. To open Computer Management, click Start, point to Run, type compmgmt.msc, and then click OK.
  6. In the console tree, expand Services and Applications, expand Message Queuing, expand Message Queuing Triggers, and then click Triggers. Your triggers are in the details pane.
  7. For each retrieval trigger that is associated with a queue on a pre-Windows XP computer, create a new trigger. For more information about creating triggers, see Create Triggers (http://go.microsoft.com/fwlink/?LinkID=101626).
  8. Configure the properties of the new trigger with the same properties as the original trigger. However, instead of using the queue from the pre-Windows XP computer for the Queue path name in the Monitored Queue section, use the new queue that you just created on the Windows XP or Windows Vista computer.

Convert the trigger to a peeking trigger

Change the trigger to a peeking trigger, and provide an application or COM object that will take care of retrieving message from the queue. Use this option if you have an application that can take care of message retrieval.

Note: You cannot use a Windows XP or Windows Vista computer for the queue being monitored (which is currently on the pre-Window XP computer). In this case, you will need an application or COM object that will retrieve the messages from the queue.

To change the trigger to a peeking trigger:

  1. Change the trigger to a “peeking” trigger. Open the Computer Management snap-in. To open Computer Management, click Start, point to Run, type compmgmt.msc, and then click OK.
  2. In the console tree, expand Services and Applications, expand Message Queuing, expand Message Queuing Triggers, and then click Triggers. Your triggers are in the details pane.
  3. For each trigger that is associated with a queue on a pre-Windows XP computer, right-click the trigger, and then click Properties.
  4. In the Message processing type section, confirm that Peeking is selected. If Peeking is not currently selected, select that option, and then click OK.
  5. Create a new rule to attach to the trigger, which, when it is triggered, will run a program that you provide to receive the messages from the queue. For more information about creating trigger rules, see Trigger rules (http://go.microsoft.com/fwlink/?LinkId=101628). For more information about Message Queuing, see About Message Queuing (http://go.microsoft.com/fwlink/?LinkId=94837).

Verify

Verify that the Message Queuing Triggers service is installed and running.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that the trigger service is installed and running:

  1. Open the Services snap-in. To open Services, click Start. In the search box, type services.msc, and then press ENTER.
  2. Scroll down the list of services to confirm the existence of the Message Queuing Triggers service.
  3. In the Status column, confirm that the Message Queuing Triggers service is Started.

Related Management Information

Trigger Operation

Message Queuing

Related:

Event ID 2215 — Trigger Operation

Event ID 2215 — Trigger Operation

Updated: January 31, 2008

Applies To: Windows Server 2008

Message Queuing Triggers is a service that you can use to associate the arrival of each incoming message at a queue with a response that depends on the contents of the message. The response may invoke either a Component Object Model (COM) component or a stand-alone executable program. These components or programs can define business rules that can be invoked in response to such messages, without any additional programming. An issue with triggers operations can, depending on the issue, prevent the invocation of some or all business rules.

Event Details

Product: Windows Operating System
ID: 2215
Source: MSMQ
Version: 6.0
Symbolic Name: MSMQ_TRIGGER_COMPLUS_REGISTRATION_FAILED
Message: The Triggers transactional component could not be registered in COM+. Error %1: %2

Resolve
Register the COM+ component

The COM+ object that was invoked by a rule is not registered correctly. To register the object again, you can use the command-line utility regsvr32.exe. For more information about using regsvr32, see article 249873 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=107513).

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To register the COM+ object:

  1. Run regsvr32.exe. To run regsvr32.exe, click Start. In the search box, type cmd, and then press ENTER.
  2. At the command prompt, type regsvr32 <your COM+ component.dll>, and then press ENTER.

Verify

Verify that the Message Queuing Triggers service is installed and running.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that the trigger service is installed and running:

  1. Open the Services snap-in. To open Services, click Start. In the search box, type services.msc, and then press ENTER.
  2. Scroll down the list of services to confirm the existence of the Message Queuing Triggers service.
  3. In the Status column, confirm that the Message Queuing Triggers service is Started.

Related Management Information

Trigger Operation

Message Queuing

Related:

Event ID 2214 — Trigger Operation

Event ID 2214 — Trigger Operation

Updated: January 31, 2008

Applies To: Windows Server 2008

Message Queuing Triggers is a service that you can use to associate the arrival of each incoming message at a queue with a response that depends on the contents of the message. The response may invoke either a Component Object Model (COM) component or a stand-alone executable program. These components or programs can define business rules that can be invoked in response to such messages, without any additional programming. An issue with triggers operations can, depending on the issue, prevent the invocation of some or all business rules.

Event Details

Product: Windows Operating System
ID: 2214
Source: MSMQ
Version: 6.0
Symbolic Name: REGISTRY_UPDATE_ERR
Message: Unable to update EventLog information in registry for ‘%1’.

Resolve
Reinstall Message Queuing triggers

A registry key may not be registered properly. Uninstall and then reinstall Message Queuing triggers.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Uninstall and reinstall Message Queuing triggers (Windows Vista)

To uninstall Message Queuing triggers:

  1. Click Start, and then click Control Panel.
  2. In the left pane, click Classic View.
  3. Click Programs and Features.
  4. In the left pane, click Turn Windows features on or off.
  5. In the Windows Features dialog box, expand Microsoft Message Queue (MSMQ) Server Core, and then clear the MSMQ Triggers box.
  6. Click OK.

To install Message Queuing triggers:

  1. Click Start, and then click Control Panel.
  2. In the left pane, click Classic View.
  3. Click Programs and Features.
  4. In the left pane, click Turn Windows features on or off.
  5. In the Windows Features dialog box, expand Microsoft Message Queue (MSMQ) Server Core, and then select the MSMQ Triggers check box.
  6. Click OK.

Uninstall and reinstall Message Queuing triggers (Windows Server 2008)

To uninstall Message Queuing triggers:

  1. Open Server Manager. To open Server Manager, click Start, point to Administrative Tools, and then click Server Manager.
  2. Start the Remove Features Wizard. To start the Remove Features Wizard, in the Features Summary section, click Remove Features.
  3. Expand Message Queuing, and then expand Message Queuing Services.
  4. Clear the Message Queuing Triggers check box, and then click Next.
  5. Click Remove.

To install Message Queuing triggers:

  1. Open Server Manager. To open Server Manager, click Start, point to Administrative Tools, and then click Server Manager.
  2. Start the Add Features Wizard. To start the Add Features Wizard, in the Features Summary section, click Add Features.
  3. Expand Message Queuing, and then expand Message Queuing Services.
  4. Select the Message Queuing Triggers check box, and then click Next.
  5. Click Install.

If you continue to get this error, note any details in the event message, and then contact Microsoft Customer Service and Support (CSS). For information about how to contact CSS, see Enterprise Support (http://go.microsoft.com/fwlink/?LinkId=52267).

Verify

Verify that the Message Queuing Triggers service is installed and running.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that the trigger service is installed and running:

  1. Open the Services snap-in. To open Services, click Start. In the search box, type services.msc, and then press ENTER.
  2. Scroll down the list of services to confirm the existence of the Message Queuing Triggers service.
  3. In the Status column, confirm that the Message Queuing Triggers service is Started.

Related Management Information

Trigger Operation

Message Queuing

Related:

Event ID 2212 — Trigger Initialization

Event ID 2212 — Trigger Initialization

Updated: December 3, 2008

Applies To: Windows Server 2008 R2

Message Queuing Triggers is a service that you can use to associate the arrival of each incoming message at a queue with a response that depends on the contents of the message. The response may invoke either a Component Object Model (COM) component or a stand-alone executable program. These components or programs can define business rules that can be invoked in response to such messages, without any additional programming. If trigger initialization fails and the trigger service is not available, any trigger-dependent message processing logic will not be carried out.

Event Details

Product: Windows Operating System
ID: 2212
Source: MSMQ
Version: 6.1
Symbolic Name: MSMQ_TRIGGER_QUEUE_NOT_FOUND
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.

Resolve
Confirm trigger queue existence and permissions

The Network Service user is the default user that the Message Queuing Triggers service runs under on Windows Server 2008 and Windows Vista. However, this user can be changed. Therefore, before you check queue permissions, confirm the user account that the trigger service runs under on the computer that hosts the queue.

Also, the trigger’s queue must be available, and the account under which the trigger service is running needs Peek and/or Receive permissions to the trigger’s queue.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Find the trigger service account

To find the account that the trigger service runs under:

  1. Open the Services snap-in. To open Services, click Start. In the search box, type services.msc, and then press ENTER.
  2. Select the Message Queuing Triggers service. Check the value in the Log On As column to determine which account the service runs under. Make a note of this account name.
  3. Right-click Message Queuing Triggers, and then click Properties.
  4. Click the Log On tab. Confirm the account that the trigger service logs on as, and modify it as necessary.

Confirm trigger queue existence and permissions

To confirm trigger queue existence and permissions:

  1. Open the Computer Management snap-in. To open Computer Management, click Start. In the search box, type compmgmt.msc, and then press ENTER.
  2. Expand Services and Applications, and then expand Message Queuing.
  3. Confirm that the queue that is monitored by the trigger exists.
  4. Right-click the queue, and then click Properties.
  5. Click the Security tab.
  6. In the Group or user names section, select the user account that the service runs under.
  7. Under Permissions, confirm that the account under which the trigger service is running has the appropriate permissions (Peek or Receive, and so on).

Verify

Verify that the Message Queuing Triggers service is installed and running.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that the Message Queuing Triggers service is installed and running:

  1. Open the Services snap-in. To open Services, click Start. In the search box, type services.msc, and then press ENTER.
  2. Scroll down the list of services to confirm the presence of the Message Queuing Triggers service.
  3. In the Status column, confirm that the Message Queuing Triggers service is Started.

Related Management Information

Trigger Initialization

Message Queuing

Related:

Event ID 2211 — Trigger Initialization

Event ID 2211 — Trigger Initialization

Updated: December 3, 2008

Applies To: Windows Server 2008 R2

Message Queuing Triggers is a service that you can use to associate the arrival of each incoming message at a queue with a response that depends on the contents of the message. The response may invoke either a Component Object Model (COM) component or a stand-alone executable program. These components or programs can define business rules that can be invoked in response to such messages, without any additional programming. If trigger initialization fails and the trigger service is not available, any trigger-dependent message processing logic will not be carried out.

Event Details

Product: Windows Operating System
ID: 2211
Source: MSMQ
Version: 6.1
Symbolic Name: MSMQ_TRIGGER_STOPPED
Message: Message Queuing Triggers service stopped.

Resolve
Resolve Event Viewer errors and restart the trigger service

There are a number of errors that can cause the Message Queuing Triggers service to stop unexpectedly. Please check the event viewer to see if there are any other events which indicate why the service may have stopped.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To resolve errors and restart the trigger service:

  1. Open Event Viewer. To open Event Viewer, click Start. In the search box, type eventvwr.msc, and then press ENTER.
  2. If any other errors were reported under Application Channel events, resolve those errors.
  3. Restart the Message Queuing Triggers service. Open the Services snap-in. To open Services, click Start. In the search box, type services.msc, and then press ENTER.
  4. In the list of services, right-click the MSMQ Queuing Triggers service, and then click Restart.

Verify

Verify that the Message Queuing Triggers service is installed and running.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that the Message Queuing Triggers service is installed and running:

  1. Open the Services snap-in. To open Services, click Start. In the search box, type services.msc, and then press ENTER.
  2. Scroll down the list of services to confirm the presence of the Message Queuing Triggers service.
  3. In the Status column, confirm that the Message Queuing Triggers service is Started.

Related Management Information

Trigger Initialization

Message Queuing

Related:

Event ID 2213 — Trigger Initialization

Event ID 2213 — Trigger Initialization

Updated: December 3, 2008

Applies To: Windows Server 2008 R2

Message Queuing Triggers is a service that you can use to associate the arrival of each incoming message at a queue with a response that depends on the contents of the message. The response may invoke either a Component Object Model (COM) component or a stand-alone executable program. These components or programs can define business rules that can be invoked in response to such messages, without any additional programming. If trigger initialization fails and the trigger service is not available, any trigger-dependent message processing logic will not be carried out.

Event Details

Product: Windows Operating System
ID: 2213
Source: MSMQ
Version: 6.1
Symbolic Name: REQUIRED_TRIGGER_DEPENDENCIES_ERR
Message: At least one of the required dependencies was not found. Please verify that MSMQ Triggers resources are dependent on Message Queue resources.

Resolve
Confirm that the trigger service can access necessary cluster resources

The Message Queuing Triggers service needs access to the required cluster resources when the Message Queuing services are configured for high availability on a Windows Server cluster. Ensure that the trigger service has access to the cluster resources that it requires.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To confirm that the trigger service can access necessary cluster resources:

  1. Open the Cluster Management snap-in. To open Cluster Management, click Start, click Control Panel, click Administrative Tools, and then click Failover Cluster Management.
  2. In the console tree, under Services and Applications, click the desired application.
  3. In the details pane, right-click Message Queuing Triggers, and then click Properties.
  4. Click the Dependencies tab.
  5. Look at the Dependencies list, and ensure that the cluster resources are in the list.

Verify

Verify that the Message Queuing Triggers service is installed and running.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that the Message Queuing Triggers service is installed and running:

  1. Open the Services snap-in. To open Services, click Start. In the search box, type services.msc, and then press ENTER.
  2. Scroll down the list of services to confirm the presence of the Message Queuing Triggers service.
  3. In the Status column, confirm that the Message Queuing Triggers service is Started.

Related Management Information

Trigger Initialization

Message Queuing

Related:

Event ID 2210 — Trigger Service Invocation

Event ID 2210 — Trigger Service Invocation

Updated: December 3, 2008

Applies To: Windows Server 2008 R2

You can use the Message Queuing Triggers service to associate the arrival of each incoming message at a queue with a response that depends on the contents of the message. The response may invoke either a Component Object Model (COM) component or a stand-alone executable program. These components or programs can define business rules that can be invoked in response to such messages, without any additional programming. If a trigger invocation fails, the message processing logic that depends on that trigger will not be carried out.

Event Details

Product: Windows Operating System
ID: 2210
Source: MSMQ
Version: 6.1
Symbolic Name: MSMQ_TRIGGER_TRANSACTIONAL_INVOCATION_FAILED
Message: Rule evaluation or execution failed for the transactional trigger %3 with the ID %4. Error %1: %2

Diagnose

The invocation of a Message Queuing trigger rule can fail for several reasons. This error might be caused by one of the following conditions:

  • A rule’s condition or action parameter is not valid.
  • The Component Object Model (COM) object that is invoked by a rule is not registered correctly.
  • The executable file that is specified in the rule could not be found or is not functional.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

A rule’s condition or action parameter is not valid

To determine the validity of a rule’s condition or action parameter:

  1. Open the Computer Management snap-in. To open Computer Management, click Start. In the search box, type compmgmt.msc, and then press ENTER.
  2. In the console tree, expand Services and Applications, expand Message Queuing, and then expand Triggers.
  3. Under Message Queuing Triggers, click Triggers.
  4. Right-click the rule that you want to execute to see its properties.
  5. Click the General tab. Confirm that the rule is pointing to the desired queue and that the processing type is correct.
  6. Click the Attached Rules tab, and ensure that the attached rules are as you intended.
  7. Under Triggers, click Rules to display a list of available rules.
  8. Right-click the rules that should be executed with the trigger, and view their properties.
  9. On the Rules Conditions tab, confirm that the rule conditions are as desired.
  10. On the Rule Action tab, confirm that the rule points to the desired action.
  11. If you determine that a rule’s condition or parameter is the problem, see the section titled “Configure rules or triggers.”

The COM object that is invoked by a rule is not registered correctly

To determine whether the COM object is registered correctly:

  1. Open the Component Services snap-in. To open Component Services, click Start, and then click Run. In the Open box, type comexp.msc, and then press ENTER.
  2. In the console tree, expand Component Services, expand Computers, expand My Computer, and then click COM+ Applications.
  3. Confirm that your COM component is present and registered.
  4. If you determine the COM object is not registered properly, then see the section titled “Register the COM+ component.”

The executable file that is specified in the rule could not be found or is not functional

To determine whether the executable file exists and is functional:

  1. Open Windows Explorer, and then browse to the executable file that is specified in the event. Confirm that the file exists and that it executes properly.
  2. Determine whether the executable file is referred to properly in the rule. Open the Computer Management snap-in. To open Computer Management, click Start. In the search box, type comexp.msc, and then press ENTER.
  3. In the console tree, expand Computer Management, expand Services and Applications, expand Message Queuing, expand Triggers, expand Rules, and then click Rules.
  4. Right-click the rule that is specified in the error message, and then click Properties.
  5. On the Rule Action tab, under Standalone executable invocation, confirm that the executable that is listed in Executable path exists and is preceded by its full path. For example, instead of just MyApp.exe, you should have c:\MyDirectory\MyApp.exe.
  6. If you determine that there is an issue with the executable file, see the section titled “Delete and recreate the rule.”

For more information about creating trigger rules, see Create and attach rules to triggers (http://go.microsoft.com/fwlink/?LinkId=104059).

Resolve
Resolve
Configure rules or triggers

Rule conditions or triggers must be configured properly. If you do not know the intended rule or trigger settings, you may want to contact your solution architect.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To confirm and change rules and triggers:

  1. Open the Computer Management snap-in. To open Computer Management, click Start. In the search box, type compmgmt.msc, and then press ENTER.
  2. Expand Services and Applications, expand Message Queuing, and then expand Triggers.
  3. Under Message Queuing Triggers, click Triggers.
  4. Right-click the rule that you want to execute, and then click Properties.
  5. Click the General tab. Confirm that the rule is pointing to the desired queue and that the processing type is correct.
  6. Click the Attached Rules tab, and ensure that the attached rules are as you intended.
  7. Under Triggers, click Rules to display a list of available rules.
  8. Right-click the rules that should be executed with the trigger, and view their properties.
  9. On the Rules Conditions tab, confirm that the rule conditions are as desired.
  10. On the Rule Action tab, confirm that the rule points to the desired action.
  11. Repeat steps 7 through 10 for each rule.

Register the COM+ object

The COM+ object that was invoked by a rule is not registered correctly. To register the object again, you can use the command-line utility regsvr32.exe. For more information about using regsvr32, see article 249873 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=107513).

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To register the COM+ object:

  1. Run regsvr32.exe. To run regsvr32.exe, click Start. In the search box, type cmd, and then press ENTER.
  2. At the command prompt, type regsvr32 <your COM+ component.dll>, and then press ENTER.

Delete and recreate the rule

The executable that is specified in the rule cannot be found or is not functional. To resolve this issue, try deleting and recreating the specified rule.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To delete and recreate a specified rule:

  1. Open the Computer Management snap-in. To open Computer Management, click Start. In the search box, type compmgmt.msc, and then press ENTER.
  2. In the console tree, expand Computer Management, expand Services and Applications, expand Message Queuing, expand Triggers, expand Rules, and then click Rules.
  3. Select the rule that is specified in the error message, and then double-click it.
  4. Ensure that you provide the full path to your executable in the rule.

For more information about creating trigger rules, see Create and attach rules to triggers (http://go.microsoft.com/fwlink/?LinkId=104059).

Verify

The Message Queuing Triggers service invocation failed. The following are possible causes:

  • The Message Queuing Triggers service is not installed or not running.
  • Triggers may not point to the correct queue, or rules may not point to the correct Component Object Model (COM) component or executable program.

Use the following procedures to verify that the Message Queuing Triggers service is installed and running and that the triggers are pointing to the right queue and the rules point to the correct COM component or executable program.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Verify that the Message Queuing Triggers service is installed and running

To confirm that the Message Queuing Triggers service is installed and running:

  1. Open the Services snap-in. To open Services, click Start. In the search box, type services.msc, and then press ENTER.
  2. Scroll down the list of services to confirm the existence of the Message Queuing Triggers service.
  3. In the Status column, confirm that the Message Queuing Triggers service is Started.

Verify that the triggers point to the correct queue and the rules point to the correct COM component or executable program

To verify that the triggers are pointing to the right queue and the rules point to the correct COM component or executable program:

  1. Open the Computer Management snap-in. To open Computer Management, click Start. In the search box, type compmgmt.msc, and then press ENTER.
  2. In the console tree, expand Services and Applications, expand Message Queuing, expand Message Queuing Triggers, and then click Triggers. Your triggers are in the details pane.
  3. Right-click the rule that you want to be executed, and then click Properties.
  4. On the General tab, under Monitored queue, confirm that the correct queue is displayed. Also, confirm that the Message processing type is correct.
  5. On the Attached Rules tab, confirm that the attached rules are correct.
  6. Return to Computer Management.
  7. Click Triggers to see a list of available rules.
  8. For each rule that should be executed with the trigger, right-click the rule, and then click Properties.
  9. On the Rule Condition tab, confirm that the conditions are as desired.
  10. On the Rule Action tab, confirm that the rule points to the desired action.

Related Management Information

Trigger Service Invocation

Message Queuing

Related:

Event ID 2209 — Trigger Service Invocation

Event ID 2209 — Trigger Service Invocation

Updated: December 3, 2008

Applies To: Windows Server 2008 R2

You can use the Message Queuing Triggers service to associate the arrival of each incoming message at a queue with a response that depends on the contents of the message. The response may invoke either a Component Object Model (COM) component or a stand-alone executable program. These components or programs can define business rules that can be invoked in response to such messages, without any additional programming. If a trigger invocation fails, the message processing logic that depends on that trigger will not be carried out.

Event Details

Product: Windows Operating System
ID: 2209
Source: MSMQ
Version: 6.1
Symbolic Name: MSMQ_TRIGGER_RULE_INVOCATION_FAILED
Message: The action defined by the rule %3 with the ID %4 was not invoked. Error %1: %2

Diagnose

The invocation of a Message Queuing trigger rule can fail for several reasons. This error might be caused by one of the following conditions:

  • A rule’s condition or action parameter is not valid.
  • The Component Object Model (COM) object that is invoked by a rule is not registered correctly.
  • The executable file that is specified in the rule could not be found or is not functional.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

A rule’s condition or action parameter is not valid

To determine the validity of a rule’s condition or action parameter:

  1. Open the Computer Management snap-in. To open Computer Management, click Start. In the search box, type compmgmt.msc, and then press ENTER.
  2. In the console tree, expand Services and Applications, expand Message Queuing, and then expand Triggers.
  3. Under Message Queuing Triggers, click Triggers.
  4. Right-click the rule that you want to execute to see its properties.
  5. Click the General tab. Confirm that the rule is pointing to the desired queue and that the processing type is correct.
  6. Click the Attached Rules tab, and ensure that the attached rules are as you intended.
  7. Under Triggers, click Rules to display a list of available rules.
  8. Right-click the rules that should be executed with the trigger, and view their properties.
  9. On the Rules Conditions tab, confirm that the rule conditions are as desired.
  10. On the Rule Action tab, confirm that the rule points to the desired action.
  11. If you determine that a rule’s condition or parameter is the problem, see the section titled “Configure rules or triggers.”

The COM object that is invoked by a rule is not registered correctly

To determine whether the COM object is registered correctly:

  1. Open the Component Services snap-in. To open Component Services, click Start, and then click Run. In the Open box, type comexp.msc, and then press ENTER.
  2. In the console tree, expand Component Services, expand Computers, expand My Computer, and then click COM+ Applications.
  3. Confirm that your COM component is present and registered.
  4. If you determine the COM object is not registered properly, then see the section titled “Register the COM+ component.”

The executable file that is specified in the rule could not be found or is not functional

To determine whether the executable file exists and is functional:

  1. Open Windows Explorer, and then browse to the executable file that is specified in the event. Confirm that the file exists and that it executes properly.
  2. Determine whether the executable file is referred to properly in the rule. Open the Computer Management snap-in. To open Computer Management, click Start. In the search box, type comexp.msc, and then press ENTER.
  3. In the console tree, expand Computer Management, expand Services and Applications, expand Message Queuing, expand Triggers, expand Rules, and then click Rules.
  4. Right-click the rule that is specified in the error message, and then click Properties.
  5. On the Rule Action tab, under Standalone executable invocation, confirm that the executable that is listed in Executable path exists and is preceded by its full path. For example, instead of just MyApp.exe, you should have c:\MyDirectory\MyApp.exe.
  6. If you determine that there is an issue with the executable file, see the section titled “Delete and recreate the rule.”

For more information about creating trigger rules, see Create and attach rules to triggers (http://go.microsoft.com/fwlink/?LinkId=104059).

Resolve
Resolve
Configure rules or triggers

Rule conditions or triggers must be configured properly. If you do not know the intended rule or trigger settings, you may want to contact your solution architect.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To confirm and change rules and triggers:

  1. Open the Computer Management snap-in. To open Computer Management, click Start. In the search box, type compmgmt.msc, and then press ENTER.
  2. Expand Services and Applications, expand Message Queuing, and then expand Triggers.
  3. Under Message Queuing Triggers, click Triggers.
  4. Right-click the rule that you want to execute, and then click Properties.
  5. Click the General tab. Confirm that the rule is pointing to the desired queue and that the processing type is correct.
  6. Click the Attached Rules tab, and ensure that the attached rules are as you intended.
  7. Under Triggers, click Rules to display a list of available rules.
  8. Right-click the rules that should be executed with the trigger, and view their properties.
  9. On the Rules Conditions tab, confirm that the rule conditions are as desired.
  10. On the Rule Action tab, confirm that the rule points to the desired action.
  11. Repeat steps 7 through 10 for each rule.

Register the COM+ object

The COM+ object that was invoked by a rule is not registered correctly. To register the object again, you can use the command-line utility regsvr32.exe. For more information about using regsvr32, see article 249873 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkId=107513).

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To register the COM+ object:

  1. Run regsvr32.exe. To run regsvr32.exe, click Start. In the search box, type cmd, and then press ENTER.
  2. At the command prompt, type regsvr32 <your COM+ component.dll>, and then press ENTER.

Delete and recreate the rule

The executable that is specified in the rule cannot be found or is not functional. To resolve this issue, try deleting and recreating the specified rule.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To delete and recreate a specified rule:

  1. Open the Computer Management snap-in. To open Computer Management, click Start. In the search box, type compmgmt.msc, and then press ENTER.
  2. In the console tree, expand Computer Management, expand Services and Applications, expand Message Queuing, expand Triggers, expand Rules, and then click Rules.
  3. Select the rule that is specified in the error message, and then double-click it.
  4. Ensure that you provide the full path to your executable in the rule.

For more information about creating trigger rules, see Create and attach rules to triggers (http://go.microsoft.com/fwlink/?LinkId=104059).

Verify

The Message Queuing Triggers service invocation failed. The following are possible causes:

  • The Message Queuing Triggers service is not installed or not running.
  • Triggers may not point to the correct queue, or rules may not point to the correct Component Object Model (COM) component or executable program.

Use the following procedures to verify that the Message Queuing Triggers service is installed and running and that the triggers are pointing to the right queue and the rules point to the correct COM component or executable program.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Verify that the Message Queuing Triggers service is installed and running

To confirm that the Message Queuing Triggers service is installed and running:

  1. Open the Services snap-in. To open Services, click Start. In the search box, type services.msc, and then press ENTER.
  2. Scroll down the list of services to confirm the existence of the Message Queuing Triggers service.
  3. In the Status column, confirm that the Message Queuing Triggers service is Started.

Verify that the triggers point to the correct queue and the rules point to the correct COM component or executable program

To verify that the triggers are pointing to the right queue and the rules point to the correct COM component or executable program:

  1. Open the Computer Management snap-in. To open Computer Management, click Start. In the search box, type compmgmt.msc, and then press ENTER.
  2. In the console tree, expand Services and Applications, expand Message Queuing, expand Message Queuing Triggers, and then click Triggers. Your triggers are in the details pane.
  3. Right-click the rule that you want to be executed, and then click Properties.
  4. On the General tab, under Monitored queue, confirm that the correct queue is displayed. Also, confirm that the Message processing type is correct.
  5. On the Attached Rules tab, confirm that the attached rules are correct.
  6. Return to Computer Management.
  7. Click Triggers to see a list of available rules.
  8. For each rule that should be executed with the trigger, right-click the rule, and then click Properties.
  9. On the Rule Condition tab, confirm that the conditions are as desired.
  10. On the Rule Action tab, confirm that the rule points to the desired action.

Related Management Information

Trigger Service Invocation

Message Queuing

Related: