从 Integration Services 目录运行时,为什么我的 SSIS 包失败并显示文件系统权限错误 [英] Why does my SSIS package fail with filesystem permission error when run from the Integration Services Catalog

查看:31
本文介绍了从 Integration Services 目录运行时,为什么我的 SSIS 包失败并显示文件系统权限错误的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个访问网络共享文件夹的 SSIS 包.如果我将此包作为 SQL 代理作业的一部分运行,它会成功.如果我直接从我的开发 PC 上的 SSIS 集成目录(右键单击并执行)运行此包,它会因权限错误而失败.如果我直接从托管 SQL 实例的服务器上的 SSIS 集成目录(右键单击并执行)运行这个包,它就可以工作.

I have an SSIS package that accesses a folder on a network share. If I run this package as part of a SQL Agent Job, it succeeds. If I run this package directly from the SSIS Integration Catalog (Right Click and execute) on my development PC, it fails with a permission error . If I run this package directly from the SSIS Integration Catalog (Right Click and execute) on the server hosting the SQL instance, it works.

参与此过程的所有用户都可以访问该文件夹(我的用户名、运行 SSIS 服务和 SQL 代理服务的用户设置).我肯定知道这一点,因为我可以访问以这些用户中的任何一个登录的文件夹.

All users's involved in this process have access to the folder (my username, the user setup to run the SSIS service and the SQL Agent service). I know this for sure because I can accsess the folders logged in under any of these users.

知道为什么会这样吗?

令我感到困惑的是,如果您从托管 SQL 实例的服务器上运行它,它会起作用,而不是从我的本地 PC(当以同一用户登录时)运行!

What baffles me is that it works if you run it from the server hosting the SQL instance, but not from my local PC (when logged in under the same user)!

我们已经到了当我们想要运行访问文件系统的某些包时,我们创建一个 SQL 代理作业来运行它.这并不理想.

We've gotten to the point that when we want run certain packages that access the file system, we create an SQL agent job to run it. It's not ideal.

推荐答案

NETWORK SERVICE 用户帐户添加到文件夹修复了该问题.我不完全确定为什么它会在用户执行包的上下文中运行,但它解决了这个问题.

Adding the NETWORK SERVICE user account to the folder fixed the issue. I'm not entirely sure why as it runs under the context of the user executing the package, but it fixed the issue.

这篇关于从 Integration Services 目录运行时,为什么我的 SSIS 包失败并显示文件系统权限错误的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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