Rule evaluation or execution failed for the transactional trigger.
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:
Open the Computer Management snap-in. To open Computer Management, click Start. In the search box, type compmgmt.msc, and then press ENTER.
In the console tree, expand Services and Applications, expand Message Queuing, and then expand Triggers.
Under Message Queuing Triggers, click Triggers.
Right-click the rule that you want to execute to see its properties.
Click the General tab. Confirm that the rule is pointing to the desired queue and that the processing type is correct.
Click the Attached Rules tab, and ensure that the attached rules are as you intended.
Under Triggers, click Rules to display a list of available rules.
Right-click the rules that should be executed with the trigger, and view their properties.
On the Rules Conditions tab, confirm that the rule conditions are as desired.
On the Rule Action tab, confirm that the rule points to the desired action.
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:
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.
In the console tree, expand Component Services, expand Computers, expand My Computer, and then click COM+ Applications.
Confirm that your COM component is present and registered.
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:
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.
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.
In the console tree, expand Computer Management, expand Services and Applications, expand Message Queuing, expand Triggers, expand Rules, and then click Rules.
Right-click the rule that is specified in the error message, and then click Properties.
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.
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).
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:
Open the Computer Management snap-in. To open Computer Management, click Start. In the search box, type compmgmt.msc, and then press ENTER.
Expand Services and Applications, expand Message Queuing, and then expand Triggers.
Under Message Queuing Triggers, click Triggers.
Right-click the rule that you want to execute, and then click Properties.
Click the General tab. Confirm that the rule is pointing to the desired queue and that the processing type is correct.
Click the Attached Rules tab, and ensure that the attached rules are as you intended.
Under Triggers, click Rules to display a list of available rules.
Right-click the rules that should be executed with the trigger, and view their properties.
On the Rules Conditions tab, confirm that the rule conditions are as desired.
On the Rule Action tab, confirm that the rule points to the desired action.
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:
Run regsvr32.exe. To run regsvr32.exe, click Start. In the search box, type cmd, and then press ENTER.
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:
Open the Computer Management snap-in. To open Computer Management, click Start. In the search box, type compmgmt.msc, and then press ENTER.
In the console tree, expand Computer Management, expand Services and Applications, expand Message Queuing, expand Triggers, expand Rules, and then click Rules.
Select the rule that is specified in the error message, and then double-click it.
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).
For more information, see Event ID 2210 ( http://technet.microsoft.com/en-us/library/dd337483(WS.10).aspx)
| Target | Microsoft.MSMQ.2008R2.Triggers | ||
| Category | AvailabilityHealth | ||
| Enabled | False | ||
| Event_ID | 2210 | ||
| Event Source | $Target/Host/Property[Type="Microsoft.MSMQ.2008R2.ServerRole"]/ServiceName$ | ||
| Alert Generate | True | ||
| Alert Severity | Warning | ||
| Alert Priority | Normal | ||
| Remotable | True | ||
| Alert Message |
| ||
| Event Log | Application |
| ID | Module Type | TypeId | RunAs |
|---|---|---|---|
| DS | DataSource | Microsoft.Windows.EventProvider | Default |
| Alert | WriteAction | System.Health.GenerateAlert | Default |
Home
<Rule ID="Microsoft.MSMQ.2008R2.Rule.Alert.Event2210" Enabled="false" Target="Microsoft.MSMQ.2008R2.Triggers" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>AvailabilityHealth</Category>
<DataSources>
<DataSource ID="DS" TypeID="Windows!Microsoft.Windows.EventProvider">
<ComputerName>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>Application</LogName>
<Expression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="UnsignedInteger">2210</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">$Target/Host/Property[Type="Microsoft.MSMQ.2008R2.ServerRole"]/ServiceName$</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</Expression>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="Alert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>1</Severity>
<AlertName/>
<AlertDescription/>
<AlertOwner/>
<AlertMessageId>$MPElement[Name="Microsoft.MSMQ.2008R2.Rule.Alert.Event2210.AlertMessage"]$</AlertMessageId>
<AlertParameters>
<AlertParameter1>$Data/EventDescription$</AlertParameter1>
</AlertParameters>
<Suppression>
<SuppressionValue>$Data/EventDisplayNumber$</SuppressionValue>
<SuppressionValue>$Data/LoggingComputer$</SuppressionValue>
</Suppression>
<Custom1/>
<Custom2/>
<Custom3/>
<Custom4/>
<Custom5/>
<Custom6/>
<Custom7/>
<Custom8/>
<Custom9/>
<Custom10/>
</WriteAction>
</WriteActions>
</Rule>