May 27, 2015 at 4:42 am
So yesterday I had to 'adept' a package to lower the amount of times it shows as failing,this job runs every 15 minutes and we're moving it over to a new monitoring system,so I was asked to make it so that it would never fail the job if a specific failure condition occurred.
Now the job no longer shows this failure,but when I look into the log I see this for the step
Executed as user: .... Microsoft (R) SQL Server Execute Package Utility Version 9.00.5000.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
Started: 10:55:21 Error: 2015-05-27 10:55:21.37 Code: 0xC0016016 Source:
Description: 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.
End Error DTExec: The package execution returned DTSER_SUCCESS (0). Started: 10:55:21 Finished: 10:57:35 Elapsed: 134.223 seconds.
The package executed successfully. The step succeeded.
I have tried everything on the article about this,nothing seems to work
May 27, 2015 at 5:00 am
Change your package and project to "Don't Save Sensitive" and redeploy. After adding suitable configuration info to supply passwords etc at run time, the error should go away.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
May 27, 2015 at 5:02 am
Hi
What ProtectionLevel is set for this Package?
Regards
Mike
May 29, 2015 at 6:34 am
I set it to don't savesensitive still seeing the message popup,job itself is not failing
May 29, 2015 at 6:36 am
Resender (5/29/2015)
I set it to don't savesensitive still seeing the message popup,job itself is not failing
Just to confirm. You changed the package and the project, setting Don't Save Sensitive for both. Then did a build and a redeploy, is that correct?
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
June 1, 2015 at 7:59 am
Phil Parkin (5/29/2015)
Resender (5/29/2015)
I set it to don't savesensitive still seeing the message popup,job itself is not failingJust to confirm. You changed the package and the project, setting Don't Save Sensitive for both. Then did a build and a redeploy, is that correct?
That solved it,there was also an option on the deploy to set the package protection level,last 2 run shows.
Executed as user: .... Microsoft (R) SQL Server Execute Package Utility Version 9.00.5000.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 15:55:20 DTExec: The package execution returned DTSER_SUCCESS (0). Started: 15:55:20 Finished: 15:55:24 Elapsed: 4.649 seconds. The package executed successfully. The step succeeded.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply