Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SSIS Packages failing when run via Scheduler Expand / Collapse
Author
Message
Posted Tuesday, June 5, 2012 11:15 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, July 22, 2013 12:50 PM
Points: 5, Visits: 17
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.
Post #1311359
Posted Tuesday, June 5, 2012 11:42 AM


Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Tuesday, June 24, 2014 12:24 PM
Points: 514, Visits: 1,717
sound likes IBM Tivoli/Maestro needs SQL Server 2008 drivers installed.
Post #1311386
Posted Wednesday, June 6, 2012 8:01 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, July 22, 2013 12:50 PM
Points: 5, Visits: 17
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!
Post #1311881
Posted Wednesday, June 6, 2012 8:09 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 5:17 AM
Points: 5,230, Visits: 9,457
What account does the IBM Scheduler run under? Does that account have access to the databases?

John
Post #1311886
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse