March 13, 2008 at 12:02 am
I have two servers server1 and Server2 both has SQL Server 2005 installed.Server1 has Enterprise Evaluation Edition
and server2 has Workgroup Edition.Since server2 has workgroup edition I cannot open the saved SSIS package in server2.
So I connected from server1 created a DTS package and saved it.After this I opened the package by connecting to
Integration services and executed the project. But I get a error
Error: The AcquireConnection method call to the connection manager "DestinationconnectionOLEDB" failed with error code 0XC0202009.
If I execute the same SSIS package with execute immediately and save SSIS package the package executes successfully.But if I
open the same saved package next time and execute I get the same error.
I even created a new SSIS package using Visual Studio.Here my requirement is to create a package and schedule the package
using the SQL Server jobs to execute the package at a required time. I can execute the package directly in the studio but
when I schedule the same package in jobs it is unable to execute. Please help me to figure out why this happens when a package
can execute successfully while the same saved package throws out error when opened in SSIS and jobs.
March 13, 2008 at 2:30 am
March 13, 2008 at 3:52 am
The Enterprise Evaluation Edition service pack on server1 is SP1 and SERVERPROPERTY('ProductLevel') is RTM.
The Workgroup Edition service pack on server2 is SP2 and SERVERPROPERTY('ProductLevel') IS RTM
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply