SSIS Packages failing when run via Scheduler

  • I just migrated my Database and SSIS packages from an old server running SQL 2005 to a new server running SQL 2008. Now, my SSIS packages are running successfully via SQL Agent but are failing when run via our Scheduler (IBM Tivoli/Maestro). Has anyone ever seen this before? Thanks for any ideas / suggestions.

    btw - this is the error I get when trying to run the package via the scheduler:

    Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "ERASE DB" failed with error code 0x80004005. There may be error messages posted before this with more information on why the AcquireConnection method call failed.

  • sound likes IBM Tivoli/Maestro needs SQL Server 2008 drivers installed.

  • Thanks for the suggestion, but I don't think the issue is drivers, unless this is something new with SQL 2008. We did not need any drivers for this job to run with SQL 2005. The SSIS package is initiated from a .bat file and this runs successfully when run from command line. It does not run when IBM Scheduler tries to kick it off. Thanks again for any additional suggestions!

  • What account does the IBM Scheduler run under? Does that account have access to the databases?

    John

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

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