April 21, 2009 at 7:41 am
I have an SSIS package that works fine in production. Then I bring it down to my PC, connect the config file to a test DB, and try and run it from BIDS. Now I'm getting the following errors and I don't know why.
The first error is "The statement has been terminated.Violation of PRIMARY KEY constraint 'My_PK'. Cannot insert duplicate key in object 'dbo.MyTable'."
The kicker with this error is the file is only 5 lines large, the column in question is NOT duplicated, and there is NO identity field on the table. Just in case, though, I removed the PK from the table, tried to execute that task again and came up with the same error.
Anyone see the above before?
Error # 2 is the dreaded "Bulk Insert Task: An error occurred with the following error message: "Cannot fetch a row from OLE DB provider "BULK" for linked server "(null)"". I'm using a flat file source and an OLE DB Connection manager for the destination. I don't see a connection timeout on the OLE DB CM (this is the only thing I was able to find on Google regarding this problem). I've checked the properties and gone into Edit. So maybe I'm blind.
But my major confusion is why the BIT would be throwing this error in test if it works fine in Production??
Any help would be greatly appreciated. Thanks in advance.
April 21, 2009 at 8:22 am
DOH!
Ignore this problem / question, please. Sorry for wasting the bandwidth.
The developer who created the package forgot to put the destination connection strings in the config file, so on those steps, the package is still looking at the wrong database even though I changed the OLE DB connection string.
DOH again. My bad.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply