Hi,

I have an SSIS Package which I build and deploy to a Database Server where I
schedule it to run daily.

When it runs it uses the Connection detauls specified in the Connection
Manager. ( I am not using any configuration file)

I can run the package locally on my PC withing Visual Studio and it runs fine.

The protection level on the Package is "EncryptSensitiveWithUserKey"

When I try to run the package on the server I get an error stating "Failed
to acquire connection TestConnection. Connection may not be configured
correctly or you may not have the right permissions on this connection ". If
I then go to the connection managers section on the package I see the
connections but the password is missing from each one. When I input it there
it works. Why is the password missing?


How do I get around this?

I have tried also using the Configuration File and I have the same problem.

(I am sue that this worked before as this package has been used for past 12
months).

Anyone know why I have this problem and how I can get around it.

"C" wrote:

When you select EncryptSensetiveWithUserKey, it is using your login's
userkey. When you then deploy that to run on the server, the server is
running the service under some other user context than you, so it cannot
decrypt the sensitive stuff (like a saved password). This is a common
occurance for SSIS users and designers.

Check out these two blogs:

http://toddchitt.wordpress.com/2008/06/30/ssis_pw/

and if you want to go with a Configuration database:
http://toddchitt.wordpress.com/2008/06/27/ssis_config/

--
Todd C

"C" wrote:

When you select EncryptSensetiveWithUserKey, it is using your login's
userkey. When you then deploy that to run on the server, the server is
running the service under some other user context than you, so it cannot
decrypt the sensitive stuff (like a saved password). This is a common
occurance for SSIS users and designers.

Check out these two blogs:

http://toddchitt.wordpress.com/2008/06/30/ssis_pw/

and if you want to go with a Configuration database:
http://toddchitt.wordpress.com/2008/06/27/ssis_config/

--
Todd C

"C" wrote:

When you select EncryptSensetiveWithUserKey, it is using your login's
userkey. When you then deploy that to run on the server, the server is
running the service under some other user context than you, so it cannot
decrypt the sensitive stuff (like a saved password). This is a common
occurance for SSIS users and designers.

Check out these two blogs:

http://toddchitt.wordpress.com/2008/06/30/ssis_pw/

and if you want to go with a Configuration database:
http://toddchitt.wordpress.com/2008/06/27/ssis_config/

--
Todd C

"C" wrote:

When you select EncryptSensetiveWithUserKey, it is using your login's
userkey. When you then deploy that to run on the server, the server is
running the service under some other user context than you, so it cannot
decrypt the sensitive stuff (like a saved password). This is a common
occurance for SSIS users and designers.

Check out these two blogs:

http://toddchitt.wordpress.com/2008/06/30/ssis_pw/

and if you want to go with a Configuration database:
http://toddchitt.wordpress.com/2008/06/27/ssis_config/

--
Todd C

"C" wrote:

When you select EncryptSensetiveWithUserKey, it is using your login's
userkey. When you then deploy that to run on the server, the server is
running the service under some other user context than you, so it cannot
decrypt the sensitive stuff (like a saved password). This is a common
occurance for SSIS users and designers.

Check out these two blogs:

http://toddchitt.wordpress.com/2008/06/30/ssis_pw/

and if you want to go with a Configuration database:
http://toddchitt.wordpress.com/2008/06/27/ssis_config/

--
Todd C

"C" wrote:

When you select EncryptSensetiveWithUserKey, it is using your login's
userkey. When you then deploy that to run on the server, the server is
running the service under some other user context than you, so it cannot
decrypt the sensitive stuff (like a saved password). This is a common
occurance for SSIS users and designers.

Check out these two blogs:

http://toddchitt.wordpress.com/2008/06/30/ssis_pw/

and if you want to go with a Configuration database:
http://toddchitt.wordpress.com/2008/06/27/ssis_config/

--
Todd C

"C" wrote:

When you select EncryptSensetiveWithUserKey, it is using your login's
userkey. When you then deploy that to run on the server, the server is
running the service under some other user context than you, so it cannot
decrypt the sensitive stuff (like a saved password). This is a common
occurance for SSIS users and designers.

Check out these two blogs:

http://toddchitt.wordpress.com/2008/06/30/ssis_pw/

and if you want to go with a Configuration database:
http://toddchitt.wordpress.com/2008/06/27/ssis_config/

--
Todd C

"C" wrote:

When you select EncryptSensetiveWithUserKey, it is using your login's
userkey. When you then deploy that to run on the server, the server is
running the service under some other user context than you, so it cannot
decrypt the sensitive stuff (like a saved password). This is a common
occurance for SSIS users and designers.

Check out these two blogs:

http://toddchitt.wordpress.com/2008/06/30/ssis_pw/

and if you want to go with a Configuration database:
http://toddchitt.wordpress.com/2008/06/27/ssis_config/

--
Todd C