September 24, 2008 at 12:22 pm
I have an SSIs package that insert data in a DB2 DB via "OLE DB Detination" control.
On my test box every thing works fine, when I promote to Prod I get this error when inserts are attempted.
"OnError,Server,ID,QuoteKey Insert,{115B39FE-1F62-4A62-AC10-75241D878497},{0A732FC3-F294-4BDB-85C3-AF7BB8F3E544},9/24/2008 12:54:53 PM,9/24/2008 12:54:53 PM,-1071611876,0x,SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "ESW.OEDW" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed."
The connection strings are stored in a SQL Server DB. The connections strings are correct, I've tested the production version of the connection string in my IDE and I'm able to "Preview" data via the "OLE DB Detination" control.
I find it odd that it works on the test box, which is not my PC, but the Prod box.
Any ideas as to the problem?
thanks
September 25, 2008 at 1:39 am
How are you reading the connection string from SQL? Via package configurations?
September 25, 2008 at 4:48 am
yes, via package configuration
September 25, 2008 at 4:58 am
When you deploy to your production box, are the production configurations found on the same location as the test configurations?
How are you dealing with saving sensitive info? Have you disabled the sensitive info?
September 25, 2008 at 5:30 am
the same table name and schema are used between the QA and Prod boxes, the name of the SQL Server DB is different, but that is stored in a XML config file. There are other config value being held in the and these are being pulled/used because I can see work being done by raw files be created.
September 26, 2008 at 3:09 pm
The configuration package should be updated with sensitive information manually. After that configuration file needs to be stored on server and added to during execution time.
September 26, 2008 at 4:28 pm
found the problem, the connection string was correct but the field which gives the datatype for the variable had an unprintable ascii character on it.
Since the package didn't know the datatype it couldn't use the connection string as an actual string and couldn't connect
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply