Question

  Asked: Mar 14 2008   7:31 AM GMT
  Asked by: MNA


Unable to execute the saved SSIS package.


SSIS, SQL Server 2005, DTS

I have two servers server1 and Server2 both has SQL Server 2005 installed.Server1 has Enterprise Evaluation Edition SP1
and server2 has Workgroup Edition SP2.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.
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.

Subscribe to Alerts! Get questions and answers delivered to your Inbox.


E-mail me updates on this question



   SUBSCRIBE

hidden modal window

Answer Wiki (Improve, edit or add to this answer)


 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0



It sounds like there is a problem decoding the credentials when opening the saved package. When you setup the package what encryption level did you select?
  • AddThis Social Bookmark Button

Browse more Questions and Answers on SQL Server.

Looking for relevant SQL Server Whitepapers? Visit the SearchSQLServer.com Research Library.


Discuss This Answer


You must be logged-in to discuss a question. Log-in/Register

Mrdenny  |   Mar 14 2008  5:22PM GMT

Check out my SQL Server blog “SQL Server with Mr Denny” for more SQL Server information.

 

MNA  |   Mar 17 2008  5:12AM GMT

I always choice Do not save sensitive data and save the project or import the saved project.