Execution of a Job Skipping Tasks When Ran from Agent

  • Hello,

    I'm running VS SSDT 2017. I made a package in SSIS that I want for the SQL Server Agent to be able to execute as part of a scheduled job in the Job Activity Monitor in SSMS. The problem that I'm having is that when I execute the package from the activity monitor, a large portion of the tasks in the package get skipped without throwing an error. The job reports as having executed successfully even though none of the work was done. It's worth mentioning that when executed manually in SSIS, the package runs all tasks exactly as intended.

    The tasks that are getting skipped by the agent all live in loop containers. The loop containers are qualified under character strings that line up with the names of files each grouping of tasks is built to ingest (Foreach Loop Editor >> Collection). When the string is detected, the filename is stored in a variable and the job proceeds with ingesting the file. I've made sure that the account the agent is using to execute the job has access to the directory where the files are stored and the files themselves, so I'm confused as to what else could be causing this.

    Does anyone have any ideas of where I could find my issue? Let me know if more info/screencaps would be helpful.

  • It's likely some data issue. When you run manually, or from the agent, are you accessing the same data sources?

    There should be logs as well you can examine.

    https://www.sqlshack.com/overview-of-ssis-package-logging/

  • It's likely some data issue. When you run manually, or from the agent, are you accessing the same data sources?

    There should be logs as well you can examine.

    https://www.sqlshack.com/overview-of-ssis-package-logging/

  • Well it still sounds like security to me. It usually is. Did you try running the job as yourself?

    Access to a directory doesn't always mean access to the files it contains.

    Are you using drive mappings or UNC for the directories?

    just some thoughts...

  • Have you checked the All Executions report?

    I suspect that the tasks are not being skipped, rather that they are not executing successfully, which would be in line with TangoVictor's post above.

    The absence of evidence is not evidence of absence
    - Martin Rees
    The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
    - Phil Parkin

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

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