Hello -
The problem is related to your package protection. The connection string requires a password and the package protection is set to "EncryptSensitiveWithUserKey" - the default setting. The only person who can decrypt & acquire the connection at run-time is you/whoever created the package.
You need to change it to "EncryptSensitiveWithPassword" OR "EncryptAllWithPassword" and set a password for the package. Say "MypkgPassword"
Ref:
Package Protection Level[
^]
Microsoft.SqlServer.Dts.Runtime.Application app;
Microsoft.SqlServer.Dts.Runtime.Package pkg;
app = new Microsoft.SqlServer.Dts.Runtime.Application();
app.PackagePassword = "MypkgPassword";
Package pkg = app.LoadPackage(pkgLocation, null);
pkgResults = pkg.Execute();
...
...
Afteryou set the password, save it, close and reopen it. Edit the connection that uses password and supply password and test connection. Then save and use it.
Excel driver does not work in 63bit environment, you need to set it to 32 bit in SQL Setver Agent
Ref:
http://sqlblog.com/blogs/john_paul_cook/archive/2010/03/24/running-32-bit-ssis-in-a-64-bit-environment.aspx[
^]
Does it have anyother connection with Windows Authentication ?
If yes Create a Proxy (you need to create credentials first) and this proxy should be used to execute the package.
Ref:
http://www.mssqltips.com/sqlservertip/2163/running-a-ssis-package-from-sql-server-agent-using-a-proxy-account/[
^]
Thanks,
Kuthuparakkal