SQL Server Performance

Package does not run with "Execute Package Task"

Discussion in 'SQL Server 2005 Integration Services' started by podgehb, Jun 27, 2007.

  1. podgehb New Member

    I have built an SSIS package (ParentPackage) that calls another package (ChildPackage). I have loaded both packages to our production SQL Server (2005 with SP2), so they are both in the MSDB database. When I run the ParentPackage from my developer PC, it runs ok: the ParentPackage calls the ChildPackage. But when I log onto the production server and run it from there, it fails.

    This is the error message I get:
    Error. Error: 0xc0014062 while preparing to load the package. The LoadFromSQLServer method has encountered OLE DB error code 0x80004005 (Login failed for user ''. The user is not associated with a trusted SQL Server connection. ). The SQL Statement that was issued has failed.

    Some points:
    (1) To make debugging easier, I removed all tasks from the packages except the Execute Package Task in the ParentPackage.
    (2) The ParentPackage is connecting to the ChildPackage using a connection object with this connection string:
    Provider=SQLNCLI.1;Data Source=MyProductionServer;Integrated Security=SSPI;Initial Catalog=MyDatabase
    (3) The production server has SQL Server 2005 Standard Edition and my machine has SQL Server 2005 Developer Edition -- could this problem be due to a feature that you need Enterprise Edition for?
    (4) I have tried it on another developer machine (with SQL Server 2005 Developer Edition) and it worked
    (5) If the package does run another package, it

    Any idea why it does not run on our production server?
  2. satya Moderator

    Should not be an edition issue, btw what is the service pack level?

    Satya SKJ
    Microsoft SQL Server MVP
    Writer, Contributing Editor & Moderator
    http://www.SQL-Server-Performance.Com
    This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.
  3. podgehb New Member

    "Service pack level" ? I have just installed SP2 (for SQL Server 2005).
  4. satya Moderator

    Then, have you tested after SP2 implementation?

    This link explains the error and gives you more links for fixing the issue:
    http://msdn2.microsoft.com/en-us/library/ms151156(SQL.90).aspx



    Satya SKJ
    Microsoft SQL Server MVP
    Writer, Contributing Editor & Moderator
    http://www.SQL-Server-Performance.Com
    This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.

Share This Page