I created a SSIS package on my computer locally.

It has an OLE DB connection to my server, using an account with
sysadmin privelages.

When I debug the package it is able to connect and runs perfectly.

However, when I create a job and specify the package on my server, the
job fails citing:

OnError, ...........The AcquireConnection method call to the connection
manager "<connection hidden for security>" failed with error code
0xC0202009.

The SQL Server Log states:

"Login failed for user '<username hidden>'. [CLIENT: <local machine>]"

Does anyone have any idea why I can establish the OLE DB connection
with my datasource when debugging, but not when it is set up as a job
on the server?

Travis:

I too have seen this type of thing pop up. I can create a package and
debug/run it OK, and even deploy it to an SSIS server instance and run it
under SSIS. But when I schedule it as a job, it fails.

Something you might want to check is when you define the job step in SQL
Server Agent, you open a drop-down list and select SSIS package. This adds a
bunch of tabs. One of them is "Data Sources". Check off the data source that
is giving you issues and manually edit the connection string as appropriate.

No guarantees. Hope this helps.

Todd C

"Travis Lowdermilk" wrote: