Post reply

Package runs fine from SSIS but errors when called from SQL Agent Job

  • December 15, 2008 at 9:05 am

    #127436

    Hi,

    I've created a packgage on the same server on which I'm deploying it. When I install the package and run it from Integration Services the package runs fine. But when I try and run it from a Sql Agent Job it fails with the following error msg below. I know it has something to do with user/password specified in my connection managers but I don't know what I could be doing wrong. I've tried using an xml config file that doesn't seem to help. Any help or suggestions would be greatly appreciated.

    Thanks in advance!

    Executed as user: MYSERVER\SYSTEM. ...ecute Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 10:36:55 AM Error: 2008-12-15 10:36:55.66 Code: 0xC0016016 Source: 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: 2008-12-15 10:36:55.66 Code: 0xC0016016 Source: 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: 2008-12-15 10:36:56.22 Code: 0xC020200E Source: Extract data and create file fo. The step failed.

  • December 15, 2008 at 9:17 am

    #912550

    That's the message you get when SQL Server Agent doesn't have permission to run the package. The Protection Level property of the package is probably set to the default EncryptSensitiveWithUserKey so only the creator can run the package. You should save the package with Protection Level property set to something else (I prefer EncryptAllWithPassword) that requires a password and provide the password to the package in the job step.

    See "Setting the Protection Level of Packages" in Books OnLine.

    Greg

  • December 15, 2008 at 10:13 am

    #912625

    Thanks! That did the trick!

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

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