Failed to complete the task. The job was called by user <user>. The last step to run was step1

Question

I created an SSIS package that works successfully and flushes data to the right place. But the same package leads to an error when I run it through work. I googled n received these links, but could not exit the game, 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

Please offer.

Answer 1

The screen captures are great, but the details will be on sublins, so in the first picture, where you expanded the [+] sign, it says: “Done as user X. Unable to open Step output file”,

If you select this line, more detailed information will be displayed in the lower panel.

General troubleshooting for something working in BIDS / SSDT but not in SQL Agent

However, as a rule, when something works in BIDS / SSDT and does not work in SQL agent, the first thing you need to pay attention to is the difference in permissions. You run the package in visual studio and your credentials are used to

• File system
• Database (unless a specific user and password is specified)
• General SaaS (Send Mail Task will use some mail node to send email)

Running things in an SQL agent job can complicate the situation, because now you have the opportunity for each individual step of the job job to run under the SQL Agent account or a delegated set of credentials set by your database administrator.

Other complications are network resources --- my K: drive may be mapped to \\ server1 \ it \ billinkc, while the SQL Server agent account may have mapped to \\ server2 \ domainAccount \ SQLServer \ or may not be displayed completely.

As mentioned in Gowdhaman008, there may also be a mismatch between 32 and 64 bits. Typically, this is specific to using Excel as the source / destination, but also its head with other specific RDBMS drivers and / or ODBC connections for the specified resources.

Specific for your example

Based on the error message snippet, my main assumption is that the CORP\CORP-MAD$ account does not have access to where the file was placed. To fix this, make sure the MAD $ account has read / write access to the location of the Happy files. Because this account ends in $, it can only exist on a computer running SQL Agent. If it accesses the network / SaaS resource, you may need to create an explicit credential for SQL Server (in the Security section), and then enable this credential for SSIS subtasks.

Secondary, less likely, that the files do not exist and that this is just a weird Send Mail error. I know that I still have a lot of hits on the parameter "address" cannot be an empty string , even if an email address is specified.

Answer 2

I assume that it works in BIDS and not in the SQL agent job. I ran into this problem and set the package property in the agent job as the next screenshot [ Use 32 bit runtime marked], and it worked for me.

Hope this helps!

Answer 3

Replication error

Error messages: job failed. The work was called for in Appendix 89 (Programación del Agente de replicación.). The final step to complete was step 3 (Detectar cierre del agente no registrado.).

Alguan idea