大网数据广告活动
启动与系统组件

Triggered runbook never completes

· 52CE 我爱测

Fixes an issue where a triggered runbook never completes in System Center Orchestrator.

This article helps you fix an issue where a triggered runbook never completes in System Center Orchestrator.

Applies to:   All versions of Orchestrator
Original KB number:   2805832

Symptoms

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.

<MsgCode>_com_error</MsgCode>
<Params>
<Param>Unspecified error</Param>
<Param></Param>
<Param>-2147467259</Param>
</Params>
</Exception></Prev>
</Exception></Prev>
</Exception>
1 Process terminated: exception caught.

Cause

This can occur if disallow results from triggers is enabled on the SQL Server.

Resolution

To resolve this issue, change the disallow results from triggers value to 0.

First run following SQL statements in SQL Server Management Studio to verify the current setting:

USE master  
XEC sp_configure 'show advanced option',1  
RECONFIGURE  
XEC sp_configure

If the value is 1, change the setting to 0 by running the following command:

EXEC sp_configure 'disallow results from triggers',0  
RECONFIGURE

More information

This issue has been corrected.

This feature will be removed in the later version of SQL Server and the recommended setting for this value is 1. For more information, see disallow results from triggers Server Configuration Option.

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
See source applicability · Source date 06/26/2024
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。