DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "Fuzzy Lookup" (60) failed with error code 0xC0202009 while processing input "Fuzzy Lookup Input" (61)

March 4, 2010 12:21 by Ryan Garaygay

Encountered this error in one of recent tasks involving SSIS Fuzzy Grouping and Lookup.

[Fuzzy Grouping Inner Data Flow : SSIS.Pipeline] Error: SSIS Error Code DTS_E_PROCESSINPUTFAILED.  The ProcessInput method on component "Fuzzy Lookup" (60) failed with error code 0xC0202009 while processing input "Fuzzy Lookup Input" (61). 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.  There may be error messages posted before this with more information about the failure.

[Fuzzy Grouping Inner Data Flow : SSIS.Pipeline] Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED.  The PrimeOutput method on component "OLE DB Source" (1) returned error code 0xC02020C4.  The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing.  There may be error messages posted before this with more information about the failure.

[Fuzzy Grouping [800]] Error: A Fuzzy Grouping transformation pipeline error occurred and returned error code 0x8000FFFF: "An unexpected error occurred.".

This is the only relevant error message or code that I got and didn't seem quite helpful.

And it appears intermittently at first, until I noticed that the error occurs at a certain number of records and although not exactly repeatable, very close to that value. around 4M rows.

While troubleshooting, tried increasing available memory (released some memory locked for another application) and the error occurred when the number of input records increased.

Tested further and the behavior seemed consistent. And it seemed that the size of the input is proportional to the memory (RAM) used. Calculated estimated size of ever row I had to be at 1KB. Tried processing 10M rows and freed up at least 10GB of RAM and it worked fine.

I can try to work-around so that I will process smaller sets/batches so i push 10M in one pass but just needed to figure out what was causing it and although not very clear from the error message I think increasing free memory did the trick for me.

Sharing in case someone else runs into a similar error. Hope this helps


Comments

April 12. 2010 23:21

components


this is really the information I was looking for, thank you my friend ....

components

April 13. 2010 22:46

top commponent


I really liked your article, ... Thanks

top commponent

April 21. 2010 22:49

stretch mark removal

Really, I like your post. Very useful for me. Actually I have been following your blog for 3 days and now I can say that I enjoy here.

Thanks

stretch mark removal

April 23. 2010 13:51

professional name badges

Thanks for the post, enjoyed it.

professional name badges

April 28. 2010 22:43

cleveland launcher iron

It’s really great post, nice blog..I would like to appreciate your work and would like to tell to my friends.

cleveland launcher iron

May 3. 2010 12:54

ed hardy discount

Thank you for the information

ed hardy discount

May 10. 2010 22:22

attacchi di panico

Finally the content of this blog is serious

attacchi di panico

May 19. 2010 19:41

1000 payday loan

Thanks for the post, enjoyed it.

1000 payday loan

Add comment


(Will show your Gravatar icon)

  Country flag

biuquote
  • Comment
  • Preview
Loading