December 16, 2011 at 8:32 am
Hi All,
Got a bit of an odd problem.
I have a data flow task which is taking an ADO.NET datasource, and writing it to an OLE DB Destination.
It's a pretty straightforward query - SELECT Fields FROM Source WHERE Conditions, nothing fancy in the conditions.
The weird part is that the write occurs successfully, and then after completing, it fails!
I've looked up this error and seen many other people with the same error, but everyone else seems to have solved it by changing their initial query from a SELECT * to a SELECT Fields query. Problem is, mine is *already* a SELECT Fields query.
The only somewhat different part about the way my query is working is that it is using an Expression to set the DataSource. However, the Expression *works*. The output that comes out is exactly what I want it to be.
For the time being I've "solved" my problem by just setting the MaximumErrorCount to a value above the number of errors produced by this "problem", which allows the package to continue.
Does anyone have any idea how I can go about fixing this problem? I don't even really know where to start!
December 16, 2011 at 8:37 am
Okay... never mind. Found the solution.
Turns out that the problem *was* actually my Expression. I had put in a template query to get my columns, and then in my Expression I had later removed one of those columns.
Forgot to remove that column from my template query, so it ended up thinking a column mapping didn't exist.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply