Ah, good old "string or binary data" - the annoying thing is that SQL must know which field and input clash caused the error, but it doesn't seem to want to tell us.

Without going out of your way to design some error-trapping, I can start you off with a couple of choices:-

1. Run just the SELECT statements from your sprocs, adding some WHERE clauses for where data is of length greater than the intended destination

2. Switch SQL Profiler on and configure it to trap and show the error

Note that #2 can be very server-intensive unless set up correctly - probably best to carry out either of these tests on a non-production copy of the data until you know what you're doing.