Post reply

Error running package from Management Studio

  • March 15, 2007 at 12:43 pm

    #117906

    Help. I am trying to run an SSIS package from Management Studio jobs. It probably has to do with passwords or something, but I am clueless where to fix.  Thanks!

    version: SQL Server 2005, sp2

    This is the error I am receiving:

    Quote:

    Message

    Executed as user: ABC\sqluser. ...  Version 9.00.3042.00 for 32-bit  Copyright (C) Microsoft Corp 1984-2005. All rights reserved.    Started:  11:21:14 AM  Error: 2007-03-15 11:21:14.73     Code: 0xC0016016     Source:       Description: Failed to decrypt protected XML node "DTSroperty" 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: 2007-03-15 11:21:14.86     Code: 0xC0016016     Source:       Description: Failed to decrypt protected XML node "PackagePassword" 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: 2007-03-15 11:21:22.18     Code: 0xC001602A     Source: Oehm Automation - Fetch a...  The package execution fa...  The step failed.

  • March 17, 2007 at 9:43 pm

    #695599

    Looks like you are reading encrypted data.

    Can you query the data through Query Window?

    MohammedU
    Microsoft SQL Server MVP

  • March 19, 2007 at 6:12 am

    #695674

    Not sure if this will help or not, but you might try going into the actual package properties and under the Security make sure the ProtectionLevel is set to Don'tSaveSensitive. Unless you want to choose (and set up) one of the security option.

     

    Hope this helps!!!

    MarkA

  • March 20, 2007 at 12:07 pm

    #696014

    If you are trying to execute the package through a job then you can try to go into SSIS and go to File > Save a Copy of >

    At the bottom is a Protection Level setting. Make sure you select 'rely on server storage and roles for access control. Now save the package to SQL Server with that setting. Then try and execute your job that points to that package you saved.

     

  • March 22, 2007 at 10:26 pm

    #696535

    even with the package u r facing the problem u can execute the same with the option 'rely on server storage and roles for access control' selected. if possible run the package using the user that have access to msdb database.

    Regards,

    Nitin'

Viewing 5 posts - 1 through 4 (of 4 total)

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