June 18, 2009 at 8:04 pm
Hi,
I have an IS package that runs fine on BIDS but fails to run when I import it in SQL management studio and run it as a job through SQL Server Agent.
I imported the package using "Rely on server storage and roles for access control".
I am using SQL Agent service account to run the package in the Agent job.
The package consistently fails with the following error.
"SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "DWP2.MIDEV" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed."
I tried creating a package configuration file with the connection managers in it and used the file before running the package from Management Studio. But still no avail.
Please advise!
Regards,
Vivek
June 18, 2009 at 10:18 pm
Hi,
Looks like a problem between 32 bits and 64 bits platforms, when you run a package in BIDS the platform used to do this is 32 bits, however when you move this in an 64 bits platform the server run into the package into 64 bits platform. so if the driver that you are use for connect to data source run only in 32 bits the package always fails. You need run the package with an job that call the SSIS for 32 bits platform.
Regards
June 18, 2009 at 11:29 pm
Hi Julio,
Thanks for your response.
My server platform is also dual processor 32 bit so its not a problem with driver portability.
However, I was using Microsoft provider for OLE DB driver. When I Switched to Oracle provider for OLE DB for my connection it ran successfully.
Regards,
Vivek
June 21, 2009 at 4:04 am
Hi there,
I had the same problem.
When I changed the datasource - just copy past it again, and re-runed the job, it worked.
give it a shot.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply