Post reply

SSIS package 'Unexpected Termination' status when running from SSISDB catalog

  • August 16, 2025 at 5:24 pm

    #4636486

    Hello,

    I'm not the one causing the unexpected termination error. I've had a SQL job that runs daily for a long time. This job executes an SSIS project. Suddenly, I started receiving the unexpected termination error. When I run it manually in Visual Studio, there's no problem. My ETL package first truncates the relevant tables and refills them with data from the Excel sources. No changes were made to the Excel or SQL tables, but it started giving me the error. I tried disabling some tasks in my ETL package and running them one by one, and I succeeded. But they don't all work at once. The latest task, BrickTarget, doesn't work at all, even when deployed individually. I'm new to this. I've encountered similar issues with other ETL packages. However, I have other packages that use .xlsx or .csv files, and they're fine at the moment. Can you help? test

  • August 16, 2025 at 5:25 pm

    #4636487

    Hello,

    I'm not the one causing the unexpected termination error. I've had a SQL job that runs daily for a long time. This job executes an SSIS project. Suddenly, I started receiving the unexpected termination error. When I run it manually in Visual Studio, there's no problem. My ETL package first truncates the relevant tables and refills them with data from the Excel sources. No changes were made to the Excel or SQL tables, but it started giving me the error. I tried disabling some tasks in my ETL package and running them one by one, and I succeeded. But they don't all work at once. The latest task, BrickTarget, doesn't work at all, even when deployed individually. I'm new to this. I've encountered similar issues with other ETL packages. However, I have other packages that use .xlsx or .csv files, and they're fine at the moment. Can you help?

    test

  • August 18, 2025 at 7:55 am

    #4637018

    Despite this being the same error message as the original post, you should really start a new thread, as it's likely a different issue causing the same error.

    You do not execute a SSIS project. You execute a SSIS package.

    If you take a look at the All Executions report, does that give you more information?

Viewing 3 posts - 16 through 18 (of 18 total)

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