SSIS package execution question in SQL agent

Hi there,

I have been trying to schedule a package I design to run off hour, but unable to do so. Here is a strange issue:

1. I was able to fully run and complete the package through VSS. My package has three steps and I have on complete arrows from one step to the next... When I run it, it does what I expected in SSIS designer.

2. I was able to deploy and run the actual package by double click on the file system and it runs successfully through Execute Package Utility.

So my package does loop through a file folder and insert records from within the folder through execute SQL task to a SQL table...etc. Typically it takes a while to run....

However, when I put the package under SQL agent and run it as a job (through setting up the sql job to call a package on the file system). It runs and completed within a few seconds.... Somehow, it didn't give me an error, but it doesn't seem like it acutally runs the package.

Does the execution of the package somehow sends success message back prematurely to SQL job Why does it not successful run

Is there any configuration setting that I am missing here How can I find out if it actually runs the package and why does it returns so quickly and claim successful, yet it didn't do anything

Please help! thanks,

Jon




Answer this question

SSIS package execution question in SQL agent

  • john hill

    Are you doing any logging from your package If not, add a log provider for text files and take a look at it after execution.

    -Jamie



  • Dietz

    Sure... So it actually failed... due to this message...

    <message>The connection "{087B883F-D188-440A-9501-FF38CF5CEC28}" is not found. This error is thrown by Connections collection when the specific connection element is not found.

    <message>Failed to acquire connection "10.0.2.2.LogDB.jhwang". Connection may not be configured correctly or you may not have the right permissions on this connection.

    But I thought I had set the connection correctly within my package (connection manager) and when I run it through the Execute Package Utility it works as well.

    Why did it failed when I try to run it under sqlagent Is there is a special setting I need to do for it to run under sql agent

    I notice within the job step when I choose the file source to point to my package... there was a tab called data sources where it has the connections I defined in my package. Does it matter if I put a check box on them or not Either way they failed to connect.

    Please help!

    Thanks!



  • John Gallagher

    Date 2/17/2006 5:43:57 PM
    Log Job History (NightlyJob)

    Step ID 1
    Server Jhwang
    Job Name NightlyJob
    Step Name ExecuteJob
    Duration 00:00:05
    Sql Severity 0
    Sql Message ID 0
    Operator Emailed
    Operator Net sent
    Operator Paged
    Retries Attempted 0

    Message
    Executed as user: OPENTABLE.COM\jhwang. The package executed successfully. The step succeeded.



  • amitdk

    Try these two simple tests:

    1. Write a very simple package to test your SQL Agent environement

    2. Use sa user in the db connection to make sure it is not something caused by Windows' Credentials.


  • santamonicali

    The linked article actually doesn't apply to my case.

    In my case, my package runs under SQL agent successfully. However, it does nothing. I didn't execute the actual package and result were not what I was expected.

    Anything else more helpful

    thanks
    Jon



  • Johnnie B.

    Read this as to how to get more useful information when running under SQL Agent: http://wiki.sqlis.com/default.aspx/SQLISWiki/ScheduledPackages.html

    -Jamie



  • SSIS package execution question in SQL agent