title: My SSIS Package works, but fails as a SSMS job (Error: 0xC0016016)
body: <p><strong>My SSIS Package works, but fails as a SSMS job (Error: 0xC0016016)</strong></p>
  
  <p>I am posting this question and sharing my solution to this issue as my own question because I didn't see the posed problem match the specific issue I encountered and the answers seemed to be scattered in different forum questions.</p>
  
  <p><em>Background:</em></p>
  
  <ul>
  <li>I have four SSIS packages on SQL Server 2012 that import a table from SQL Server 2008 R2, 2008, or 2005, depending on the specific package. I use a designated sql server login and password for the source database and integrated Windows security for the target database.</li>
  <li>Within SSIS I am able to run each package without a problem.</li>
  <li>To ensure this package ran on a schedule, I set up a SSMS job on the same server as the SSIS package. In Job step properties, I chose: SQL Server Integration Services Package > run as SQL Sever Agent Service Account > Package source: File system).</li>
  </ul>
  
  <p><em>The Symptom:</em>
  When manually running the job to make sure it worked, I got an error and saw this in the Log File Viewer.  This was the first of several errors, but as this was chronologically the first error, I looked into this one first.</p>
  
  <ul>
  <li><em>Error:</em> 2014-10-24 09:52:34.48</li>
  <li><em>Code:</em> 0xC0016016</li>
  <li><em>Source:</em> [Redacted -- the correct name of the table I was importing]</li>
  <li><em>Description:</em> Failed to decrypt protected XML node "DTS:Password" 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.</li>
  <li>End Error</li>
  </ul>