Microsoft.ACE.OLEDB.16.0升级SSIS意外终止
我们在 SSIS 目录服务器中安装了 SSIS 包。在目录服务器中,安装了 Microsoft.ACE.OLEDB.12.0
。这些工作运行良好,没有出现任何问题。我们正在导入 Excel 模板。
我们的连接字符串如下所示:
Provider=Microsoft.ACE.OLEDB.12.0;数据 源=\UNCPATH\Report_Template.xlsx;扩展属性=“EXCEL 12.0” XML;HDR=YES";
现在,他们已将目录服务器 ACE 驱动程序版本升级到 Microsoft.ACE.OLEDB.16.0 64 BIT。 随着目录服务器的升级,软件包因“意外终止”而失败。查看消息时,验证与 Excel 目标相关的数据流任务期间失败。
相同的包在 VS 本地以及本地目录服务器中运行良好。在本地,我也有 Office 365 64 位。
不确定为什么它仅在具有 Microsoft.ACE.OLEDB.16.0 的目录服务器上失败。
- 这是由于可安装 Microsoft.ACE.OLEDB.16.0 64 位吗?
- Office 64 位是否有不同的 ACE 驱动程序?
We have SSIS package installed in SSIS catalog server. In the catalog server, Microsoft.ACE.OLEDB.12.0
is installed. The jobs were running fine without issues. We are importing into Excel Template.
Our connection string looks like below:
Provider=Microsoft.ACE.OLEDB.12.0;Data
Source=\UNCPATH\Report_Template.xlsx;Extended Properties="EXCEL 12.0
XML;HDR=YES";
Now, they have upgraded the catalog server ACE driver version to Microsoft.ACE.OLEDB.16.0 64 BIT.
With the upgrade in catalog server, the packages are failing with "UnExpected Termination". When looking into the messages, it is failing during validation of the Data Flow Task related to excel destination.
The same package is running fine locally in VS and also in local catalog server. In locally also, I have Office 365 64 bit.
Not sure, why it is failing only on the catalog server with Microsoft.ACE.OLEDB.16.0.
- Is this due to installable of Microsoft.ACE.OLEDB.16.0 64 bit ?
- Is office 64 bit having different ACE driver ?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
该错误是由于 SQL Server 和 Office 安装不同造成的。
如果 Office 的安装是“单击以运行”安装,则 SQL Server 无法访问访问提供程序。
该问题可以通过以下任一方法解决。
OLEDB 驱动程序问题解决
The error is due to different installations of SQL Server and Office installation.
SQL Server is not able to access the Access provider, if the installation of office was Click to Run installation.
The issue can be resolved by any of the following approaches.
OLEDB driver issues resolution