Failed to decrypt protected XML node

Hi,

I,ve been searching the forum for answers to this error but with no luck:

Failed to decrypt protected XML node "DTSassword" 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.

Setup:
I'm running the packages from the SQL Job Agent - the packages are stored in the file system. The agent is using a proxy account to get the right permissions. I know this because the job has run for severel weeks without errors. The package is calling other packages and is using configuration files. It was actually more than on job that failed (with the same error) - but not all the jobs.

Now it is saying that it can not "find the file specified" - what file would that be? - I'm wondering if it is a package file or a configuration file or maybe another file. It dosn't give me any other information to where the problem is.

Any help is appreciated!

Regards
Simon
What's the ProtectionLevel on the package?|||It has never been changed so it is EncryptedByUserKey - but it is on the same computer with the same user and it has been running so I don't think that it is the problem, but maybe I'm wrong?!?!
|||

The only time I have seen this is when another developer updated the package, and saved it with his user key. That doesn't seem to be true in your case, though.

As a workaround, try changing it to EcryptSensitiveWithPassword, and see if that works better.

|||Thanks for you reply.
I will probably do that - it is only that there is a bunch of packages that I have to go through to changes the setting.

If anybody can give me the reason for this error I would be happy :-S
|||

jwelch wrote:

The only time I have seen this is when another developer updated the package, and saved it with his user key. That doesn't seem to be true in your case, though.

As a workaround, try changing it to EcryptSensitiveWithPassword, and see if that works better.

As I don't have any sensitive data in the package but instead store this information in configuration files I changed the setting to: DontSaveSensitive.

I afterwards started the packages which ran succesfully. I've earlier tried just to open a package and afterwards save it and the error would go away. So I will monitor the package to see if it fails again at a later time.

Thanks jwelch for your help.