July 20, 2022 at 5:42 pm
I have a SQL Server Job that calls out to a *.dtsx file. When this runs, I keep getting an error stating "The step did not generate any output. The return value was unknown. The process exit code was -1073741819. The step failed." However, this doesn't happen all the time, just every once in a while. However, when this error occurs, if I log onto the server, and double click the *.dtsx file, that SSIS Window opens, and I execute the package, and everything works great.
What is causing this issue when running through the SQL Job Agent as it doesn't seem like anything is wrong with the package itself since I can run it successfully?
July 21, 2022 at 6:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
July 21, 2022 at 7:08 pm
can you post the exact command line you are using to execute the package - as well as the job step definition.
depending on how its being executed you may be loosing the log - and if so you will need to change how you execute the package
July 21, 2022 at 7:30 pm
If I go into the "Command Line" tab for the Job Step, I see this: "/FILE "\"\\dev01\Integation Packages\Status_Data_Import.dtsx\"" /CHECKPOINTING OFF /REPORTING E". This isn't anything I set, nor does it appear I can change.
My apologies, but not sure what you mean by "Job Step Definition". I just have the following:
Type: SQL Server Integration Services Package
Run As: SQL Server Agent Service Account
Package: File System. \dev01\Integation Packages\Status_Data_Import.dtsx
The rest is simply the defaults when setting up this step.
July 21, 2022 at 8:32 pm
have a look at this link https://techcommunity.microsoft.com/t5/sql-server-support-blog/ssis-package-fails-with-error-the-step-did-not-generate-any/ba-p/318301
and check windows event log.
July 26, 2022 at 2:38 pm
I made the changes to the registry, but still the same error message. Thank you for suggesting it though..
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply