How to test an SSIS package with "DontSaveSensitive" Protection Level inside of BIDS

  • I'm trying to debug an already existing package whose ProtectionLevel is set to "DontSaveSensitive" and where package configuration is enabled.

    I needed to add some code to this package and now that I'm trying to run it in BIDS to test my changes, I can't seem to.

    Every time I run the package, the config file is deleted and then of course the package can't figure out the username and password to my Oracle connection manager.

    Is there a way to test a package in BIDS once it has been compiled with a DontSaveSensitive protection level and where package configuration is enabled?

  • You could (temporarily) change the package protection level to something else like Encrypt with User Key or password. Then enter a username/password. Don't forget to change it back when you are done.

    Otherwise, get a copy of the config file and put it in EXACTLY the same path as it is looking for..

    CEWII

  • I changed the package to EncryptAllWithPassword and that worked.

    As for the suggestion of using the exact path of the config file, my issue was that the config file was deleted by SSIS every time I ran the package.

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

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