How to determine the cause of error in job when error message only gives process exit code -1073741819

Question

How to determine the cause of error in job when error message only gives process exit code -1073741819

Shakirin 0

I am facing the issue where the SSIS package fails when running via job agent and the error would be :

The step did not generate any output. The return value was unknown. The process exit code was -1073741819. The step failed.

And this issue only happens intermittently, and upon rerunning it without changing anything would pass the job. I do found this article below but I am unsure how to determine whether this is the same issue i am facing or is it caused by other issues

https://techcommunity.microsoft.com/blog/sqlserversupport/ssis-package-fails-with-error--the-step-did-not-generate-any-output-the-return-v/318301

0 comments

2 answers

Your answer

Answer 1

Your exit code -1073741819 is 0xC0000005 (access violation) , the host process crashed. That's a different failure than the -1073741502 in the Microsoft blog you linked, so its desktop-heap "SharedSection" registry fix probably won't help you.

The intermittent "fails as a job, passes when run manually" pattern fits an access violation: the package body usually completes, then the process crashes, which is why reruns succeed and the SSIS log shows no task error.

To confirm your specific cause: check the Windows Application event log at the failure timestamp and find the faulting module that DLL name is the real culprit.

Answer 2

The exit code -1073741819 by itself does not identify the root cause. To determine the cause, more detailed logging from the SSIS package and SQL Server Agent is required.

Use these approaches:

Enable SSIS logging inside the package
Configure SSIS logging and log providers in the package so that execution details and failures are captured. By default, packages do not log anything. Once logging is enabled, the logs will show the actual error (for example, permissions, decryption, connection failure) instead of only the generic exit code.
Run the package via DTExec with verbose console logging
Instead of the SSIS job step type, use a CmdExec step that calls dtexec.exe with verbose reporting and console logging, and capture the output:
```
   dtexec.exe /FILE "C:\Path\YourPackage.dtsx" /REPORTING V /CONSOLELOG NCOSGXMT
```
In the job step, use the Advanced options to:
- Redirect output to a file, and/or
- Enable Include step output in history
The console logging will return detailed error messages (for example, cryptographic or permissions errors) that explain why the package failed.
Use SQL Server Agent Log File Viewer and SSISDB reports
For packages stored in MSDB, SSIS Package Store, or local folders:
- In Object Explorer, right‑click the job → View History.
- In Log file summary, locate the failed execution, expand the job node, and select the step to see detailed messages.
For packages in SSISDB:
- In the job history message, note the Execution ID.
- In Object Explorer, expand Integration Services Catalogs → SSISDB.
- Right‑click SSISDB → Reports → Standard Reports → All Executions, then locate that execution for detailed runtime information.
Check for known causes when running under SQL Server Agent
Once detailed errors are available, compare them with common Agent‑specific issues:
- ProtectionLevel and decryption failures when the Agent account differs from the package author.
- Missing permissions for file shares, registry keys, or external resources.
- Integrated security connections failing because the Agent account lacks required SQL or OS permissions.
Excel / ACE and multi‑threading issues (if applicable)
If the package uses Excel sources/destinations or ACE providers, exit code -1073741819 can be associated with multi‑threaded Excel components. A known workaround is to:
- Execute Excel components sequentially instead of in parallel, or
- Split them into separate packages and trigger via Execute Package Task with ExecuteOutOfProcess set to True.

By combining SSIS logging, DTExec verbose output, and Agent/SSISDB reports, the intermittent failures can be correlated to a specific error (permissions, configuration, provider, or multi‑threading) rather than relying on the generic exit code.

References: