Thanks for the reply. I tried changing it to ServerStorage but now VS won't let me save the package. I get:
The protection level, ServerStorage, cannot be used when saving to this destination...
Main Topics
Browse All TopicsHello experts,
The package runs successfully in Visual Studio but when I try to schedule it to run in a job, I am getting the following error:
Failed to decrypt protected XML node "DTS:Property" 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.
I am using protection level EncryptSensitiveWithPasswo
Articles I have found regarding this error say to change the protection level from EncryptSensitiveWithUserKe
Any help is appreciated.
Thanks!
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I found the solution.
The problem is that even though the protection level is set to EncryptSensitiveWithPasswo
Publish the package to the server (Items 7 and 8 are the key!!) -
1) Connect to Integration Services for the desired server.
2) Open the MSDB folder (or subfolder thereof) where the package is to be imported.
3) Right-Click the folder and select Import Package.
4) Select File System in Package location.
5) Browse to the .dtsx file, select it and click Open.
6) Click into the Package name box. The package name will be automatically inserted.
7) Click the button next to Protection level.
8) Ensure that Encrypt sensitive data with password is selected and enter the password.
9) Click OK in both dialogs to finish.
Create the job -
1) Under the SQL Server Agent, create a new job and add a job step.
2) Set the Type to "SQL Server Integration Services Package".
3) Select the server and the package you just imported.
4) Schedule the job.
The package will now run successfully.
Contrary to many comments I found on the subject in various forums, it is not necessary set the Type to "Operating System (CmdExec)" in the job step in order to pass the password to the package on the command line each time the job is executed. The password is stored with the package on the server.
Business Accounts
Answer for Membership
by: St3veMaxPosted on 2009-03-03 at 11:45:11ID: 23787609
Try setting it to 'Server Role' when you deploy the package; as the server will take care of permissions.
HTH