脚本任务使用此版本的Integration Services不支持的15.0版脚本 [英] The Script Task uses version 15.0 script that is not supported in this release of Integration Services

问题描述

大家好，

我们正在将SSIS项目从SQL 2012迁移到SQL 2016.项目已成功升级，没有任何问题，并且能够运行少量软件包而没有任何错误。但是很少有包得到脚本任务而且失败了。错误消息
如下： -

错误：从XML加载脚本任务时出现异常：System.Exception：脚本任务"ST_bb19096e98ab45d2a2d6132b995cd509"使用此版本不支持的15.0版本脚本。
Integration Services。要运行包，请使用"脚本任务"创建新的VSTA脚本。在大多数情况下，当您在％SQL_PRODUCT_SHORT_NAME％Integration Services中打开SQL Server Integration Services包时，会自动转换脚本

以使用受支持的版本。 at $ $ $ $ $ Microsoft $。$。$ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $ $从BIDS （VS2015）运行时运行正常。如果从BIDS部署项目并运行代理作业，它也可以正常运行。但是当部署通过.ispac（部署）文件发生时，会发生此错误。有人可以建议如何
超过此错误吗？

迁移或SSIS 2016是否存在任何已知问题？

谢谢。

解决方案

您好Nagesh，

我建议的迁移路径永远不会跳过SQL 2012版本 - > SSIS 2014然后到SQL 2016

但不知道脚本中的内容似乎是"创建新的VSTA脚本"的建议。这意味着在SSIS 2016中重写它是明智的，特别是当你说只有几个包失败时。

这可能是一个错误，所以如果你能正确记录它提交一个项目到
MS Connect 。

Hi All,

We are migrating an SSIS project from SQL 2012 to SQL 2016. The project upgraded successfully without any issues and able to run few packages without any errors. But there are few packages which has got the script task and they are failing. The error message is as below: -

Error: There was an exception while loading Script Task from XML: System.Exception: The Script Task "ST_bb19096e98ab45d2a2d6132b995cd509" uses version 15.0 script that is not supported in this release
of Integration Services. To run the package, use the Script Task to create a new VSTA script. In most cases, scripts
are converted automatically to use a supported version, when you open a SQL Server Integration Services package
in %SQL_PRODUCT_SHORT_NAME% Integration Services. at
Microsoft.SqlServer.Dts.Tasks.ScriptTask.ScriptTask.Load
FromXML(XmlElement elemProj, IDTSInfoEvents events)

This runs fine when run from BIDS (VS2015). It also runs fine if the project is deployed from BIDS and run through agent job. But when the deployment happens through .ispac (deployment) file, this error occurs. Can somebody suggest how to get past this error?

Is it any known issues with migration or with SSIS 2016?

Thanks.

解决方案

Hi Nagesh,

My suggested migration path is to never skip a version SQL 2012 --> SSIS 2014 then to SQL 2016

But not knowing what is in your script it seems that the suggestion to "create a new VSTA script" which means to rewrite it when in SSIS 2016 is sensible, especially when you say only several packages fail.

It could be a bug so if you can properly document it submit an item to MS Connect.

这篇关于脚本任务使用此版本的Integration Services不支持的15.0版脚本的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！