SSIS, SQL Agent, Credential, Proxies and the -1073741515 process exit code

  • Articolo

Recently I have been dealing with a really weird error while trying to execute a SSIS package using a SQL Agent Job with a concrete user credential. The error that I've got was:

Executed as user: XXXXX. The step did not generate any output. The return value was unknown. The process exit code was -1073741515. The step failed.

And that's all!

Ok, I had in mind a hypothesis regarding the root cause: the user privilegies. The user was not managed/created by myself so the first thing I've done was to try to understand where was what the lack of permmisions?  After some research on the error code, no relevant information was found. Then, I've converted the error code to its exadecimal equivalent and I got some information but nothing directly related to SQL Agent and SSIS. The -1073741515 is the ERROR CODE 0xC0000135 (STATUS_DLL_NOT_FOUND). It looks that the job had some issues loading DLLs...

Because the Job was designed to launch a SSIS package I opted to check the permissions on the "C:\Program Files\Microsoft SQL Server\110\DTS\Binn" folder where the DTExec.exe is located and VOILA!, the user does not had permissions to read/execute in that directory!. This lead me to understand that the user was created without being included in the "Local Users Group" of the machine where needs to run software... An error in my opinion.

Hope this helps!

Comments

  • Anonymous
    July 28, 2014
    There could be other causes - the target machine does not have the dll available due to the different version. e.g. dot net framework version 4.0 and 4.5

  • Anonymous
    November 18, 2014
    I have this problem happen randomly.  I have a job that runs every 15 minutes via SQL Agent Job.  A couple times randomly throughout the day I get a "The step did not generate any output.  The return value was unknown.  The process exit code was -1073741819.  The step failed."  so if it was a permissions issue with a folder I would think it would fall in the 'it runs or it doesn't' category.

  • Anonymous
    April 22, 2016
    I had job scheduled to run as 32 bit mode. I unchecked the settings and let it run int 64 bit mode. It worked for me. Hope that helps.