"Row yielded no match during lookup" while there is no row going through the Looku

Hi all,

I don't understand what's happening here.

I have a Conditional Split with 3 outputs. On the first output I have a lookup, when I execute the package I have 56 rows going through the Conditional Split, all rows are then going to the 2nd and 3rd output but the lookup on the first output generates an error "Row yielded no match during lookup".

I don't understand why the lookup is generating an error while there is no row going through it.

Any idea ?

Sbastien.

As an image worth more than a thousand words... http://www.mediamax.com/sebnunes/Links/98B4724720

|||

I have no idea why is that happening; but have you try to configure errors in the lookup task to redirect them? just to see if there is something going through it....just a thought

Rafael Salas

|||Yes I did, there is no row redirected in the Error output either :-\|||

Am I the only to have this behaviour ? I'm stuck here, how a transformation could raise an error while there is no row going through it ? It's nonsense isn't it ?

Any idea how to workaround this ?

|||I've found the problem, it's just the Designer which was messed up. I have 2 different lookup transformation with the same query and the designer was highlighting (in red in Debug Mode) one of the Lookup transformation as the one causing the error but in fact the error was happening in the other Lookup transformation.