SSIS Error when running SQL Job but no error when running Package

Discussion:

(too old to reply)

2009-02-23 15:30:04 UTC

Hi,

I have an SSIS Package imported into Integration Services Maintenance Plans
folder.

When I run the SSIS Package from Integration Services it works fine.

When I schedule a SQL Job which calls the SSIS Package it fails with error
"Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The
AcquireConnection method call to the connection manager "TestConnection"
failed with error code 0xC0202009"

Anyone know why I get an error only when I run it as a SQL Job?

2009-02-23 17:15:04 UTC

Permalink

My SSIS Package runs fine as a SQL Server Job on a different server.

The only difference is that the server it does not work where I get problem
in below post is that this server is using SQL Server Instances.

Post by C
Hi,
I have an SSIS Package imported into Integration Services Maintenance Plans
folder.
When I run the SSIS Package from Integration Services it works fine.
When I schedule a SQL Job which calls the SSIS Package it fails with error
"Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The
AcquireConnection method call to the connection manager "TestConnection"
failed with error code 0xC0202009"
Anyone know why I get an error only when I run it as a SQL Job?

hfdev

2009-02-26 19:09:01 UTC

Permalink

C, check to see if the SQL Agent job on the server where the package runs
successfully is configured to run as a domain account that has permissions on
the SQL db that your package is trying to connect to.

Maybe the SQL Agent is configured to run as local system on the server where
it is failing.

HTH,
--
Josh Blair (hfdev)
HydraForce, Inc.

Post by C
My SSIS Package runs fine as a SQL Server Job on a different server.
The only difference is that the server it does not work where I get problem
in below post is that this server is using SQL Server Instances.