SSIS 包卡在“创建的执行"处地位 [英] SSIS Package Stuck at "Created Execution" Status

查看:51
本文介绍了SSIS 包卡在“创建的执行"处地位的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我最近为我的一个 SSIS 项目部署了更新,自从该项目失败后,它就按计划运行.

I recently deployed a update to one of my SSIS projects, and ever since the project has failed it's scheduled runs.

SSIS 包似乎停留在已创建执行"状态.报告中没有消息来解释这个问题.

The SSIS package appears to be stuck at the "Created Execution" status. There are no messages in the reports to explain this issue.

我已尝试重新部署该项目,但结果保持不变.为了让系统重新上线,我最终不得不恢复到部署的早期版本,但我现在无法更新项目.

I've attempted to redeploy the project, but the results remain the same. I ultimately had to revert to an earlier version of the deployment in order to bring the system back online, but I am now in a position where I can not update the project.

我现在不知道如何解决这个问题,而这个项目对我们的业务来说是一个相当重要的组成部分.

I'm at a loss right now as to how to resolve this issue, and this project is a rather vital component to our business.

任何指导将不胜感激.

推荐答案

为了对这个问题有一个实际的答案并且我自己刚刚遇到了这个非常令人沮丧的问题,问题在于包/环境参数.当一个包按计划运行时,如果没有提供所需的包参数,SSIS 只是......坐在那里.未报告任何错误,但包从未真正启动.

In the interest of having an actual answer on this question and having just run into this very frustrating issue myself, the problem lies in package/environment parameters. When a package is run on a schedule, if required package parameters are not supplied, SSIS just... sits there. No errors are reported, but the package never actually starts.

为所需参数提供值将解决此问题.

Providing values for the required parameters will resolve this issue.

这篇关于SSIS 包卡在“创建的执行"处地位的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆