作业失败.该作业由用户< user>调用.运行的最后一步是step1 [英] The job failed. The job was invoked by user<user>. The last step to run was step1

问题描述

http://social. msdn.microsoft.com/Forums/zh-CN/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 Agent作业中运行事物会使事情变得复杂，因为您现在可以在SQL Agent帐户或您的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:驱动器可能已映射到\\ server1 \ it \ billinkc，而SQL Server代理帐户可能已将其映射到\\ server2 \ domainAccount \ SQLServer \，或者完全没有映射.

Further complicating matters are network resources---my K: drive might be mapped to \\server1\it\billinkc whereas the SQL Server Agent Account might have it mapped to \\server2\domainAccount\SQLServer\ 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.

基于错误消息的片段，我的主要假设是帐户CORP\CORP-MAD$无权访问文件放置的位置.要解决此问题，请确保MAD $帐户对放置Happy文件的位置具有读/写访问权限.由于该帐户以$结尾，因此它可能仅存在于运行SQL Agent的计算机上.如果它正在访问网络/SaaS资源，则可能需要在SQL Server中(在安全性"下)创建一个显式的凭据，然后为SSIS子任务授权该凭据.

Based on the fragment of the error message, my primary assumption is that the account CORP\CORP-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.

这篇关于作业失败.该作业由用户< user>调用.运行的最后一步是step1的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！