On my SSIS package I have 2 connection managers, both are connecting to an Oracle db. I enter in the ID and Password then click 'test connection' I'm able to connect to the database fine. I then go to a data flow of one of my control flow task. Open up my OleDb Source and click preview. The SQL query executes with no issues. I can see the data from my connection manager source.
I then go and run the package and I get this error message:
[OLE DB Source [1]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "OracleConnection" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
I've been racking my brain on this for a few days and still no luck on getting this to work.
You probably have the 'protection level' property of the package set to 'dontsavesensitive'. You could either change this to 'encryptsensitivewithuserkey' or set the password property of the connection manager through a configuration.
|||I've done both, changed the package property and tried a config file and I get the same results.
|||Enable package logging, or if you are using BIDS, check the progress tabs and see if you any warning about package configurations.Package configuration should solve the problem. This KB article has some related info:
http://support.microsoft.com/kb/918760|||
I got it working actually now, well sort of.
I had to remove all of my connection managers, close down BIDs open it back up, add new connection managers, change the package property setting again and it work.
Now I'm running into another issue
I have one package (dtsx file) that calls other dtsx file (all within the same solution) and its unable to connect to the packages it needs to call, though all the packages are in the same solution and the same database
|||Please provide more details:How are you running the packages (BIDS, DTEXEC, etc)?
Where are the packages stored?
Error messages?|||
I'm trying to run it in BIDS right now and I get this error message:
Error: Error 0xC0012050 while preparing to load the package. Package failed validation from the ExecutePackage task. The package cannot run. .
If I deploy them to my SQL server and try to execute it from there (right click, execute), I'm getting this error message:
Error: Error 0xC0012050 while preparing to load the package. Package failed validation from the ExecutePackage task. The package cannot run. .
and I list of warnings saying it can't find the connection manager and so on.
|||You have a problem here. If you remove a connection manager; you need to go to every single place where that connection manager was being referenced and provide a new/valid connection manager.The message you are getting indicates that the package failed validation; that means SSIS won't even try to run it. You need to remove all the references to that connection manager(s) you deleted.|||
This is driven my insane.
I can now run the SSIS package in BIDS, but I get the error:
'the acquireconnection method call to the connection manager 'oracle' has failed
and I've removed all of the connection managers used and created new ones and I still get the above error on my SQL server
No comments:
Post a Comment