1

I have created an SSIS package (08) that has a script task which runs an SSRS report (08) with given parameters. The report creates a pdf version of the file on a file share drive of my choosing.

When I run the SSIS manually it works perfectly, however, when I upload SSIS into SQL and then run it from the job agent it fails. It gives a long error message but the basic piece is;

(0xC0016016 Source: Description: 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. End Error

Error: 2018-01-15 16:09:58.28 Code: 0xC001600C
Source: PackageSchedule Connection manager "ReportServer08"
Description: Server authentication failed. This error occurs when login credentials are not provided, or the credentials are incorrect. )

I have tried to change the "ProtectionLevel" to "EncryptSensitiveWithPassword" and also "Donset upSensitive".

I setup a subscription to the report just to make sure it wasn't a read/write error to the specific folder and the subscription ran without error as well.

Any help on this would be greatly appreciated.

Jayasurya Satheesh
  • 7,826
  • 3
  • 22
  • 39
Marie
  • 11
  • 1
  • You're on the right track with your troubleshooting but when you created the subscription to test r/w access, did you use the same account that is also running the SQL Agent? – billinkc Jan 16 '18 at 17:02
  • Check out this KB:https://support.microsoft.com/en-us/help/918760/ssis-package-does-not-run-when-called-from-a-sql-server-agent-job-step – TheGameiswar Jan 16 '18 at 17:04

2 Answers2

0

According to this SO answer the issue was related to a date type issue. You could be experiencing the same thing

Mazhar
  • 3,797
  • 1
  • 12
  • 29
0

Thank-you for the feedback. I was able to figure it out. On Import of the package to SQL itself I changed the 'Protection Level' to 'Rely on server storage and roles for access control'. This allowed the job to execute successfully and everything looks great!

Marie
  • 11
  • 1