Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
Triggered Runbook never completes in System Center 2012 Orchestrator
Article ID: 2805832 - View products that this article applies to.
A Runbook uses the ‘invoke method’ to trigger a child Runbook. The triggered Runbook never finishes and in the policy module log the process shows as terminated.
2012-07-31 16:49:05  1 Process terminated: exception caught.
This can occur if disallow results from triggers is enabled on the SQL Server.
To resolve this issue, change the disallow results from triggers value to ‘0’.
First run following SQL statements in SQL Management Studio to verify the current setting:
XEC sp_configure 'show advanced option',1
If the value is ‘1’, change the setting to ‘0’ by running the following:
EXEC sp_configure 'disallow results from triggers',0
This issue has been corrected in System Center 2012 Orchestrator Service Pack 1 (SP1).
Note that this feature will be removed in the next version of SQL server and that the recommended setting for this value is ‘1’:
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.