Hi guys, I am new to SSIS and have a job scheduled to run everyday using SQL Agent. It has been working fine, but now, it runs and I get this error. Package Utility Version 9.00.4035.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 07:00:04 Error: 2010-11-02 07:31:42.45 Code: 0xC0016016 Source: Description: Failed to decrypt protected XML node "DTS:Password" with error 0x80070002 "The system cannot find the file specified.". 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: 2010-11-02 07:31:42.45 Code: 0xC0016016 Source: Description: Failed to decrypt protected XML node "DTS:Password" with error 0x80070002 "The system cannot find the file specified.". 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 DTExec: The package execution returned DTSER_FAILURE (1). Started: 07:00:04 Finished: 07:35:. The step failed. The strangest thing is that all my packages actually perform their tasks and my data gets updated, but in the Job History, it keeps showing as failed, so I would like to find out if someone can help me out with this and suggest a way to solve this. I have read a few posts on this, and have already made sure my main package is set to not saving sensitive. Please remember I am a newcomer to SSIS :) Thanks

Hi If you are using SSIS 2005 - you need to save the packages as Do Not save sensitive - which you are doing. When you import the package into the SSIS system you need to make sure you alter the package protection level there to do not save sensitive too. IN 2008 this is the default. Seth http://lqqsql.wordpress.com

Hi Seth, Yes, I am using SSIS 2005. My packages are set to Do Not save sensitive, and even when I import the package into the SSIS system I have set it to Do Not Save sensitive as well, but I still get the same error message

Hi Seth, You were right, I had two packages that were not set to "Do Not save sensitive". I have changed them and now my SQL Agent job runs well. Thanks

That was someting I learnt the hard way too. The good news is SQL 2008 r2 has a default protection level of - "do what the package says"http://lqqsql.wordpress.com