SSIS Package execution through SQL Server Agent Jobs

• mohan.bndr

  SSCrazy

  Points: 2360

  More actions

  January 11, 2013 at 5:58 am

  #287711

  I am try to execute the SSIS package through the jobs. When I schedule it as a job, it fails getting error 12291. But an individual package runs fine.

  I have many other SSIS packages scheduled on the same server using the same security. What can be wrong, or where can I look to find out what the problem is?

  Please suggest to resolve.

• Ant-Green

  SSC Guru

  Points: 113536

  More actions

  January 11, 2013 at 6:04 am

  #1576240

  http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=SQL%20Server&ProdVer=10.0&EvtID=12291&EvtSrc=SQLISPackage100&LCID=1033

  Possible Causes

  There are many possible causes for a package to stop running. This message might appear because of one of the following problems:

  The data sources, files, or credentials that were specified on the development computer are not available or are not valid on the computer on which the package was deployed.

  Data providers that were available on the development computer are not available on the computer on which the package was deployed. Or, data providers that were available in 32-bit versions are not available when the package is run as a 64-bit package.

  The permissions that are required by the package are not sufficient when the package is scheduled in a SQL Server Agent job.

• SQLRNNR

  SSC Guru

  Points: 281334

  More actions

  January 11, 2013 at 7:15 am

  #1576283

  Can you provide more info?

  Jason...AKA CirqueDeSQLeil
  _______________________________________________
  I have given a name to my pain...MCM SQL Server, MVP
  SQL RNNR
  Posting Performance Based Questions - Gail Shaw[/url]
  Learn Extended Events