none
Lookup error with code 0x80070057

    Question

  • Hi there,

    I'm currently designing an ETL process and I'm using lookup transformations.
    In one of them, I encountered an 0x80070057 error which I cannot explain.
    When I'm looking at the number of rows already processed, the number is not always the same when the error occurs. This is the first strange thing. A second strange thing is the explanations given by SSIS (log):

    OnError,DWHAPP1,AWW\RS9906,ODSTran1_1_1_DFT1,{002D0747-8F3E-43EF-A0EA-FE925E668ECB},{BAF1A259-7A26-49ED-B4E5-4BB9BB0BF004},08/03/2006 13:01:15,08/03/2006 13:01:15,-1073450974,0x,
    The ProcessInput method on component "ODSTran1_1_1_D1_LU2" (15452) failed with error code 0x80070057. The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running.

    I really don't get it :-(

    To explain you a bit what I'm doing, I do a lookup to check if the codes used in the facts (transaction table) exist in the referential tables (dimensions). The lookup in which the problem appears is a simple select on a table.

    If someone has an explanation or (better) a solution, shoot! :-)

    Renaud

    Wednesday, March 08, 2006 12:23 PM

All replies

  • I reply to myself :-)

    I've just tried by removing the transformation linked to the Lookup Error path and by making my transormations in another way and it seems to be ok now.

    So definetely, there was a random error (because not always at the same moment. I.e. not always with the same data) linked to the Lookup Error path and the way the Lookup managed it.

    Still strange to me because the error wasn't explicit at all and the solution is more a workaround than a real solution to a real problem.

    Bug ? This is definetely an open question :-)

    • Proposed as answer by ETL vs ELTL Tuesday, July 19, 2011 11:08 AM
    Thursday, March 09, 2006 10:47 AM
  • When you hooked up the component to the lookup's error output did you configure the output to redirect rows on error?

    Thanks,

    Matt

    Thursday, March 09, 2006 5:10 PM
  •  Matt David wrote:

    When you hooked up the component to the lookup's error output did you configure the output to redirect rows on error?

    Thanks,

    Matt

    Yes, I did so first of all but I had to change it to 'ignore failure' and used a workaround to avoid the random error.

    The workaround works fine, so I won't waste my time on looking for the real explanation of it.

    Thanks Matt :-)

    • Proposed as answer by ETL vs ELTL Tuesday, July 19, 2011 11:08 AM
    Friday, March 10, 2006 8:23 AM