• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 619
  • Last Modified:

SSIS Package AcquireConnection Error

I have an SSIS package that is returning the error message:

The AcquireConnection method call to the connection manager 'conn' failed with error code 0xC0202009

This is an OLE DB connection using the MIcrosoft version of the Oracle OLE DB driver.

I have verified that the connection works in Visual Studio, and have set the package property ProtectionLevel to EncryptAllWithPassword.

Any ideas?
0
cgulka
Asked:
cgulka
  • 8
  • 5
2 Solutions
 
HoggZillaCommented:
Save the package with ProtectionLevel to Rely On Server Storage and see if it works. If you save with a Password then you need to provide that password when you create the Job for SQL Server Agen.
0
 
HoggZillaCommented:
Also, in your connection manager, make sure you select "Allow Saving of Password".
0
 
cgulkaAuthor Commented:
The connection ais allowing for password saving.  I can't save the package on the server, so I am saving it to a dtsx file.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
HoggZillaCommented:
When you call it you will have to supply a password. What means are you using to execute? If you double click on the file it should open a configuration window that will result in creating the command line. Try this, it will allow you to enter your password for the file that you created when you saved the package.
0
 
cgulkaAuthor Commented:
That is exactly how I am running the package, and when I run it with the password is when I get the error.
0
 
HoggZillaCommented:
OK, just to be clear. We are talking about the password YOU choose when you save the SSIS package with ProtectionLevel.
0
 
HoggZillaCommented:
Here are m screenshots. Choose Save Copy of Package as...
You may already be doing this exactly correct but i want to make sure we are on the same page.

protection-level-pwd2.bmp
save-copy-to-file-pwd.bmp
0
 
HoggZillaCommented:
When I run the package or attempt to configure, I have to provide the Password I created. Are you here so far?
enter-my-pwd.bmp
0
 
cgulkaAuthor Commented:
Yes, I have done all this.  The error comes when the package tries to execute.
0
 
HoggZillaCommented:
OK, past the Script Task code here. I see the specific error referring to "conn" which is the name of a connection object in your task. Let's see where we get from there.
0
 
cgulkaAuthor Commented:
OK, so I have narrowed down the problem.  It seems to happen only when I load the user and password from a .dtsconfig file.  I'm assuming that SSIS won't use the password from that file since it isn't encrypted.  Does this sound right?  If so, how do I get past this?
0
 
cgulkaAuthor Commented:
OK I've figured it out.  When creating the .dtsconfig file, the password is not saved, you have to put it in manually.  Problem solved.
0
 
HoggZillaCommented:
Very good.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

  • 8
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now