how to run SSIS from SQLServer Agent (File System..)

  • Hi, all

    I'm learning all ways of SSIS deployment and tried to run my working package from Agent

    selecting:

    Package source: = File System,

    then browsing to myPackage.dtsx,

    then setting Data Source (check in)

    then putting into schedule

    And It's not running ...

    I have a local server installation, first it ran under domain/MlastName user and I got error

    <<SQLServer Error: 15404, Could not obtain information about Windows NT group/user 'domain\domain user',>>

    Then after switching to run this job as <SA> I got actually warning, In Job Activity Monitor I see it = Failed and I didn't see my table being changed (that what my pack does) and I can test it OK from BIDS.

    In error log I see those 2 entries with yellow triangle exclamation mark:

    [163] 1 operations applied (0 remaining)

    [162] Internal request (from SetJobNextRunDate [reason: schedule will not run again]) to deactivate schedule 13

    In Job Activity Monitor I see it = Failed

    I'm dying to make it work. I did not did any deployment if this package into SSISDB with purpose to make it test.

    What I'm missing ?? Do I need any SQL Server Browser being started ? ( now I have sql, ssis, Agent running)

    Thansk all

    Mario

    Thanks

    Mario

  • Which version of SSIS are you using?

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • Salut, Koen !!!!!!!!!!!!

    Thanksk for your helping hand!!.

    I did this package on VS 2010, running SQLS 2012, I tried pretty much everything, can run from Agent but only thru SSISB catalog.

    can ran it thru dtexec /F.

    But still can't make it thru SQL Agent from File System. As mentioned I have <Failed> in Job activity monitor, and those 2 lines in error log:

    [163] 1 operations applied (0 remaining)

    [162] Internal request (from SetJobNextRunDate [reason: schedule will not run again]) to deactivate schedule 13

    Tried on both deployed (to SSISDB) and stand alone packages, both Package and Project level connection mngr.

    Microsoft Visual Studio Tools for Applications 3.0

    Microsoft SQL Server Integration Services Designer Version 11.0.5058.0

    Visual Studio 20110 Shell (Integrated) ENU Service Pack 1.

    This service pack is for Visual Studio 2010 Shell (Integrated) - ENU.

    Microsoft SQL Server 2012 - 11.0.5058.0 (X64)

    Developer Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

    Best

    Mario

  • Try converting the project to the package deployment model.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • Thanks, and then still deploy ?

    dtexec.exe /F works OK without any deployment.

    M

  • mario17 (11/4/2014)


    Thanks, and then still deploy ?

    dtexec.exe /F works OK without any deployment.

    M

    With file system "deployment" you just copy the package to the file location where you want them.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

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

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