I have been having a major problem scheduling my SSIS packages under
SQL Agent. I have created a credential, a database logon with full
access to MSDB and a proxy for these accounts to launch the packages.
This is the same domain account that creates the packages. The
packages are loaded on SQL Server in MSDB, the ProtectionLevel of the
packages is default - EncryptSensitiveWithUserKey.

When I am logged onto the server, as the user who created the packages
and scheduled them, the SQL Agent fires the job and it runs perfectly.
When I logoff the server and the SQL Agent runs the job it fails
immediately with a "File not found" error. Occasionally it has had a
few successful runs, but on the whole it fails when I am logged off and
the SQL Agent fires the job.

I have been unable to find any help on this issue and would appreciate
anyone with advice and assistance for this ongoing and fustrating
issue. Thanks.

The solution so far has been to schedule the SQL Agent to run under the
domain account that created the packages and used in the credential,
database logon and SQL Agent proxy accounts...


ianhopewell (AT) gmail (DOT) com wrote: