December 19, 2012 at 8:40 am
I get the following error with one of my packages:
Error: The package is encrypted with a password. The password was not specified, or it is not correct.
The package connects to an AS400 so it is necessary to save sensitive with user password.
If I select save sensitive with user password, build a deployment and run the manifest it does not prompt me for the password.
If I select Save all with user password I get the error listed below.
What is strange is I have another package that is almost identical to the one that I'm having trouble with (pulls from different library) and I don't have any issues with it.
Any help would be greatly appreciated.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
December 19, 2012 at 10:12 am
I use "Don't save sensitive" and Package configurations for user names and passwords. Works like a charm.
December 19, 2012 at 10:51 am
Daniel Bowlin (12/19/2012)
I use "Don't save sensitive" and Package configurations for user names and passwords. Works like a charm.
I take it that you do not use DB2 or Oracle in your packages?
I must specify a package password on the DB2 Connection or I get an error.
There are other reason that you may want or need to encypt as oppsed to Don't Save Sensitve.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply