作业失败.作业由用户<用户>调用.运行的最后一步是 step1 [英] The job failed. The job was invoked by user<user>. The last step to run was step1
问题描述
我已经创建了成功运行的 SSIS 包并将数据转储到所需的位置.但是当我通过作业运行它时，相同的包会导致错误.我在谷歌上找到了这些链接，但没有找到出路-http://social.msdn.microsoft.com/Forums/en-US/sqltools/thread/9034bdc4-24fd-4d80-ad8d-cc780943397a/
I have created SSIS package which is running successfully and dumping the data to the required place. But the same package results in the error when i run it through job. I googled n got these links but failed to get the way out- http://social.msdn.microsoft.com/Forums/en-US/sqltools/thread/9034bdc4-24fd-4d80-ad8d-cc780943397a/
http://www.progtown.com/topic390755-error-at-start-job-the-job-was-invoked-by-user-sa.html
请推荐.
推荐答案
屏幕截图很棒，但细节会出现在子行上，所以在第一张图片中，你已经展开了 [+] 符号和它说以用户 X 身份执行.无法打开 Step 输出文件"
The screen captures are great but the detail is going to be on the sublines, so in the first picture, where you have expanded the [+] sign and it says "Executed as user X. Unable to open Step output file"
如果您选择该行，通常会在底部窗格中显示更多详细信息.
If you select that row, there is generally more detail displayed in the bottom pane.
也就是说，通常当某些东西在 BIDS/SSDT 中起作用而在 SQL Agent 中不起作用时，那么首先要看的是权限的差异.您正在 Visual Studio 中运行该包，并且您的凭据用于
That said, generally when something works in BIDS/SSDT and does not in the SQL Agent, then the first thing to look at is the difference in permissions. You are running the package in visual studio and your credentials are used for
- 文件系统
- 数据库(除非提供了特定用户和通行证)
- 通用SaaS(发送邮件任务会使用一些邮件主机来传输邮件)
在 SQL 代理作业中运行事物可能会使事情复杂化，因为您现在可以在 SQL 代理帐户或 DBA 建立的一组委托凭据下运行每个作业的单独作业步骤.
Running things in a SQL Agent job can complicate things as you now have the ability for each job individual job step to run under the SQL Agent account or a delegated set of credentials your DBA has established.
更复杂的问题是网络资源---我的 K: 驱动器可能映射到 \server1itillinkc 而 SQL Server 代理帐户可能将它映射到 \server2domainAccountSQLServer 或者它可能完全未映射.
Further complicating matters are network resources---my K: drive might be mapped to \server1itillinkc whereas the SQL Server Agent Account might have it mapped to \server2domainAccountSQLServer or it might be entirely unmapped.
正如 Gowdhaman008 所提到的，也可能存在 32 位与 64 位不匹配的情况.通常，这特定于将 Excel 用作源/目标，但也会与其他 RDBMS 特定驱动程序和/或 ODBC 连接用于所述资源.
As Gowdhaman008 mentioned, there can also be a 32 vs 64 bit mismatch. Generally this is specific to using Excel as a source/destination but also rears its head with other RDBMS specific drivers and/or ODBC connections for said resources.
根据错误消息的片段，我的主要假设是帐户 CORPCORP-MAD$ 无权访问放置文件的位置.要解决此问题，请确保 MAD$ 帐户对放置 Happy 文件的位置具有读/写访问权限.由于该帐户以 $ 结尾，因此它可能只存在于运行 SQL 代理的计算机上.如果它正在访问网络/SaaS 资源，您可能需要在 SQL Server 中创建一个显式凭据(在安全下)，然后为 SSIS 子任务授权该凭据.
Based on the fragment of the error message, my primary assumption is that the account CORPCORP-MAD$ does not have access to the location where the file has been placed. To resolve that, ensure the MAD$ account has read/write access to the location the Happy files have been placed. Since that account ends in $, it might only exist on the computer where SQL Agent is running. If it's accessing a network/SaaS resource, you might need to create an explicit Credential in SQL Server (under Security) and then authorize that Credential for SSIS subtasks.
次要的、不太可能的可能性是文件不存在，这只是一个奇怪的发送邮件错误.我知道我仍然在 参数 'address' 不能是空字符串，即使提供了电子邮件地址.
A secondary, less likely, possibility is that the files don't exist and that's just a weird Send Mail error. I know I still get plenty of hits on The parameter 'address' cannot be an empty string even though an email address is provided.
这篇关于作业失败.作业由用户<用户>调用.运行的最后一步是 step1的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
