Microsoft (R) SQL Server Execute Package Utility Version 10.50.4000.0 for 32-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. NULL
When you create a connection in SSIS and provide password for that it encrypt the password with user key.
So if you create the package then the password will be encrypted with your windows user id. And the password is only decrypt-able if the package is run by your windows account.
But when a package is run through Sql Server Agent Job it uses the windows account that is configured for the Sql Server agent. If this account is different than the account you used to create the package then exception like yours is thrown.
There are couple of ways to avoid this exception.
Never save sensitive information in the package. Set "Do not save sensitive" for package protection level. Use configuration or other ways to store the password
Run the Sql Server agent with the user account that created the package.
I prefer the first one.
If your SQL Server is 64 bit
In SQL Server JOB-->Properties-->Steps--->
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.