Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I created a package on my SQL Server (2012) through the import/export data wizard which exports data to another SQL Server (2008).

I set up a job which runs this package but I get an error:

Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Key not valid for use in specified state."

I found suggestions to set the Protection Level to "DontSaveSensitive", but after running it again on the job, I get this new error:

"Login failed for user 'username'.".

Note, running it on it's own / manually, it works fine. It is only failing on the job.

Any help is appreciated.

share|improve this question

This was a permissions issue. I changed the user account of sql server agent to Admin and it worked.

However, as I learned, this is a bad security practice, so I'd appreciate if there are other ideas out there to get around this.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.