Post reply

SSIS Package: The step did not generate any output. The return value was unknown. The process exit code was -1073741790. The step failed.

  • May 6, 2011 at 6:30 pm

    #249932

    I have created three SSIS packages in a project to handle report subscriptions in SQL Server SSRS 2008.

    One package that is triggered by the ReportServer table dbo.Subscriptions to handle new or updated report subscriptions. It works. It is not run as a SQL Agent job.

    The other two are run from a single SQL Server Agent job.

    The one that fails, loops through for each report. Logs into YouSendIt. Uploads the report file. This package works in Visual Studio. It works when I run the package directly in Management Studio. It fails when executed as a SQL Agent job.

    The puzzler is that the second package uses the same loop container to loop through the reports and archives those that have been marked as sent. I use the file attributes to mark the file as sent. It runs successfully as a SQL Agent job. It is in the same job as the one that fails.

    The return error for the job is:

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

    It cannot be a directory or file permissions issue. The successful archive report package proves that. It uploads successfully when run in VS or directly from Management Studio.

    My thoughts are that it has to do with the script task. When disabled or if there are no reports to process, the script task is not executed. The package runs successfully in SQL Agent job. But, why does it work in VS and directly?

    Thanks for your ideas.

    (58.30115757480578, -134.4143772125244)

  • May 7, 2011 at 9:41 am

    #1321384

    See if there are any messages in the Job Step History - there should be.

    You should also turn on Package Logging and enable Errors, Warnings, and other events to be logged to a table.

    Todd McDermid - SQL Server MVP, MCTS (SQL 08 BI), MCSD.Net
    My Blog - Dimension Merge SCD Component for SSIS - SSIS Community Tasks and Components

  • August 25, 2011 at 1:50 am

    #1372972

    Hi

    I have same error

    How did you solved your problem

    Can you help me please?

  • August 25, 2011 at 2:37 am

    #1372992

    Use the DTS exec utility to execute the package and see what errors it gives. you can also take help of output log files as well as profiler on the destination where this package hits.

  • November 7, 2017 at 3:59 am

    #1966956

    thomas.briscoe - Friday, May 6, 2011 6:30 PM

    I have created three SSIS packages in a project to handle report subscriptions in SQL Server SSRS 2008.One package that is triggered by the ReportServer table dbo.Subscriptions to handle new or updated report subscriptions. It works. It is not run as a SQL Agent job.The other two are run from a single SQL Server Agent job.The one that fails, loops through for each report. Logs into YouSendIt. Uploads the report file. This package works in Visual Studio. It works when I run the package directly in Management Studio. It fails when executed as a SQL Agent job.The puzzler is that the second package uses the same loop container to loop through the reports and archives those that have been marked as sent. I use the file attributes to mark the file as sent. It runs successfully as a SQL Agent job. It is in the same job as the one that fails.The return error for the job is:The step did not generate any output. The return value was unknown. The process exit code was -1073741790. The step failed.It cannot be a directory or file permissions issue. The successful archive report package proves that. It uploads successfully when run in VS or directly from Management Studio.My thoughts are that it has to do with the script task. When disabled or if there are no reports to process, the script task is not executed. The package runs successfully in SQL Agent job. But, why does it work in VS and directly?Thanks for your ideas.

    I got the same error with SSIS 2016. The way I was able to bypass the issue was in the Data Flow Task, use the "Advanced Editor for ODBC Source" (I am sure it applies to all data sources) then select the "Component Properties" tab. Then, change the "BatchSize" I reduced it to 500 and increase the "LobChunkSize", I increased it to 131072.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply