Share via

The SQL Server Management studio no longer shows running SSIS packages

Igor Gelin 0 Reputation points
2025-12-19T21:51:23.88+00:00

Hi everyone,

I run a bunch of SSIS packages in a SQL Server Agent job. The packages are deployed as files in the file system. They are executed as SQL Server Agent Service Account. I used to be able to see them under Running Packages. Today, they weren't shown there, but they were running.

User's image

Why can't I see them anymore?

Thank you for your help.

Igor

SQL Server Integration Services
0 comments

Answer recommended by moderator

Akhil Gajavelly 1,830 Reputation points Microsoft External Staff Moderator
2026-02-02T07:50:09.93+00:00

Hi @Gelin, Igor,

Thanks for your patience, and sorry for the delay in getting back to you.

This isn’t a permission issue. SSMS cannot list SSIS packages that are executed by SQL Server Agent. The Running Packages node only shows packages started from the same SSMS session, and there is no permission that enables visibility for Agent-run packages.

If it seemed to work earlier, it was likely due to a manual execution or a cached SSMS session. For Agent-executed packages, please rely on Job Activity Monitor, job history, or SSIS logging.

Thanks,
Akhil.

Was this answer helpful?

0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Yitzhak Khabinsky 27,196 Reputation points
    2026-01-06T01:39:34.6466667+00:00

    Hi @Igor Gelin,

    Here is the answer you might be not expecting.

    Starting from SSIS 2012 onwards, i.e. 2014, 2016, 2017, 2019, 2022, and 2025, the recommended way to setup SSIS run-time environment is to use Integration Services Catalog and SSISDB database. Please see below.

    The running SSIS packages and their entire history are visible via SSIS Reports for the Integration Service Catalog in SSMS.

    SSIS packages file deployment method is kept for backward compatibility with the obsolete SSIS 2005 - 2008R2. That's why there is no need to connect at all to SSIS Service in SSMS.

    ssis-database-and-catalog

    Was this answer helpful?

    0 comments
  2. Akhil Gajavelly 1,830 Reputation points Microsoft External Staff Moderator
    2025-12-22T05:47:37.9966667+00:00

    Hi @Igor Gelin ,

    This is by design. Running Packages in SSMS only shows SSIS packages started manually from SSMS, not those executed by SQL Server Agent.

    Since your packages are running via an Agent job, they won’t appear there. Use Job Activity Monitor, job history, or package logging to track them.

    Nothing is wrong with your setup.

    Thanks,
    Akhil.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.