SQL server 2014 SSIS package fails when run as sql server agent job

  • Hi all

    I have a package which runs perfectly fine when excuted as package but it fails when i calll it through agent job .

    package

  • That's most likely because you are running the package using your credentials which has rights to run the package and the SQL Agent (which runs as a Windows service) is using an account that does not have rights to run that package or some component of it.

    Can you post the error that you are getting when you attempt to run the package using the SQL Agent?

    "I cant stress enough the importance of switching from a sequential files mindset to set-based thinking. After you make the switch, you can spend your time tuning and optimizing your queries instead of maintaining lengthy, poor-performing code."

    -- Itzik Ben-Gan 2001

  • Are you overriding any of the package variables in the agent job? That's known to cause a slew of problems.

  • i m running job using sql server agent service acccount . n given the permision also to this nt account ..

    also i tried proxy account

  • Are there any error messages in the job history?

    If so, can we see them?

  • Executed as user: ********\SYSTEM. Microsoft (R) SQL Server Execute Package Utility Version 12.0.2000.8 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 11:27:30 AM Error: 2015-09-02 11:27:31.04 Code: 0xC0016016 Source: Package Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. End Error Error: 2015-09-02 11:27:31.20 Code: 0xC0202009 Source: Package Connection manager "SERVERNAME.USERNAME" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80040E4D Description: "Login failed for user 'USERNAME'.". End Error Error: 2015-09-02 11:27:31.20 Code: 0xC020801C Source: Load Dump OLE DB Destination [409] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Servername.username" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2015-09-02 11:27:31.20 Code: 0xC0047017 Source: Load Dump SSIS.Pipeline Description: OLE DB Destination failed validation and returned error code 0xC020801C. End Error Error: 2015-09-02 11:27:31.20 Code: 0xC004700C Source: Load Dump SSIS.Pipeline Description: One or more component failed validation. End Error Error: 2015-09-02 11:27:31.20 Code: 0xC0024107 Source: Load Dump Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 11:27:30 AM Finished: 11:27:31 AM Elapsed: 0.265 seconds. The package execution failed. The step failed.

    This is the error we are getting

  • By default packages store passwords encrypted based on the user who built it.

    See https://support.microsoft.com/en-us/kb/918760 and specifically the ProtectionLevel item. They need to edit the package to do one of the things noted in the article.

  • Yes they are using some machenism in Package itsel to encrypt and decrypt././

Viewing 8 posts - 1 through 7 (of 7 total)

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