Hello there

I havs ssis who transfer data between two databases.

The process worked fine until i change the password on the destination
databasse.

Since then it won't work: after i set on Protection level: Service storage
and try to save the package it brings me an error:

....cannot be used when saving to this destination. The system could not
verify that the destination supports secure storage capability...

however it allows me to create copy on SSIS and it seems ok.

when i run the package manually from file system or from server it works
fine.

But when i run the package via code it brings me an error: login failed for
user 'user'.

does somebody have an idea whats wrong?

Hello Roy:
This is a common issue with SSIS Developers. They create a package that runs
in BIDS but does not run when deployed. I see that you have been toying with
the Protection Level property. The default is "Save Sensetive with user key"
so when you try to run it from the file system (using DTExec) you are running
it under YOUR credentials (user key) so the runtime engine has what it needs
to decrypt a stored password (for a connection string somewhere in the
package).

You might want to try the Protection Level of "Save Sensetive With Password"
then in the code that you use to call the package, use a \DECRYPT switch to
include the password.

Read BOL on the DTEXEC utility for more.

HTH
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Roy Goldhammer" wrote:

Hello Roy:
This is a common issue with SSIS Developers. They create a package that runs
in BIDS but does not run when deployed. I see that you have been toying with
the Protection Level property. The default is "Save Sensetive with user key"
so when you try to run it from the file system (using DTExec) you are running
it under YOUR credentials (user key) so the runtime engine has what it needs
to decrypt a stored password (for a connection string somewhere in the
package).

You might want to try the Protection Level of "Save Sensetive With Password"
then in the code that you use to call the package, use a \DECRYPT switch to
include the password.

Read BOL on the DTEXEC utility for more.

HTH
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Roy Goldhammer" wrote:

Hello Roy:
This is a common issue with SSIS Developers. They create a package that runs
in BIDS but does not run when deployed. I see that you have been toying with
the Protection Level property. The default is "Save Sensetive with user key"
so when you try to run it from the file system (using DTExec) you are running
it under YOUR credentials (user key) so the runtime engine has what it needs
to decrypt a stored password (for a connection string somewhere in the
package).

You might want to try the Protection Level of "Save Sensetive With Password"
then in the code that you use to call the package, use a \DECRYPT switch to
include the password.

Read BOL on the DTEXEC utility for more.

HTH
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Roy Goldhammer" wrote:

Hello Roy:
This is a common issue with SSIS Developers. They create a package that runs
in BIDS but does not run when deployed. I see that you have been toying with
the Protection Level property. The default is "Save Sensetive with user key"
so when you try to run it from the file system (using DTExec) you are running
it under YOUR credentials (user key) so the runtime engine has what it needs
to decrypt a stored password (for a connection string somewhere in the
package).

You might want to try the Protection Level of "Save Sensetive With Password"
then in the code that you use to call the package, use a \DECRYPT switch to
include the password.

Read BOL on the DTEXEC utility for more.

HTH
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Roy Goldhammer" wrote:

Hello Roy:
This is a common issue with SSIS Developers. They create a package that runs
in BIDS but does not run when deployed. I see that you have been toying with
the Protection Level property. The default is "Save Sensetive with user key"
so when you try to run it from the file system (using DTExec) you are running
it under YOUR credentials (user key) so the runtime engine has what it needs
to decrypt a stored password (for a connection string somewhere in the
package).

You might want to try the Protection Level of "Save Sensetive With Password"
then in the code that you use to call the package, use a \DECRYPT switch to
include the password.

Read BOL on the DTEXEC utility for more.

HTH
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Roy Goldhammer" wrote:

Hello Roy:
This is a common issue with SSIS Developers. They create a package that runs
in BIDS but does not run when deployed. I see that you have been toying with
the Protection Level property. The default is "Save Sensetive with user key"
so when you try to run it from the file system (using DTExec) you are running
it under YOUR credentials (user key) so the runtime engine has what it needs
to decrypt a stored password (for a connection string somewhere in the
package).

You might want to try the Protection Level of "Save Sensetive With Password"
then in the code that you use to call the package, use a \DECRYPT switch to
include the password.

Read BOL on the DTEXEC utility for more.

HTH
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Roy Goldhammer" wrote:

Hello Roy:
This is a common issue with SSIS Developers. They create a package that runs
in BIDS but does not run when deployed. I see that you have been toying with
the Protection Level property. The default is "Save Sensetive with user key"
so when you try to run it from the file system (using DTExec) you are running
it under YOUR credentials (user key) so the runtime engine has what it needs
to decrypt a stored password (for a connection string somewhere in the
package).

You might want to try the Protection Level of "Save Sensetive With Password"
then in the code that you use to call the package, use a \DECRYPT switch to
include the password.

Read BOL on the DTEXEC utility for more.

HTH
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Roy Goldhammer" wrote:

Hello Roy:
This is a common issue with SSIS Developers. They create a package that runs
in BIDS but does not run when deployed. I see that you have been toying with
the Protection Level property. The default is "Save Sensetive with user key"
so when you try to run it from the file system (using DTExec) you are running
it under YOUR credentials (user key) so the runtime engine has what it needs
to decrypt a stored password (for a connection string somewhere in the
package).

You might want to try the Protection Level of "Save Sensetive With Password"
then in the code that you use to call the package, use a \DECRYPT switch to
include the password.

Read BOL on the DTEXEC utility for more.

HTH
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Roy Goldhammer" wrote: