Debug record by record until you find the offender, and check each field of the record against the db columns?
–
JimNov 14 '12 at 14:43

Please provide more information for example code sample, Data Structure and DataType of the fields you are trying to import.. this will make it easier in my opinion to lend some sort of direction
–
MethodManNov 14 '12 at 14:43

1

There is no way you can debug record by record using EF. It is performed as one transaction.
–
monstroNov 14 '12 at 14:58

Thanks, Just tried, but with catch is not intercepting the exception.
–
monstroNov 14 '12 at 15:26

1

If this error is not raised in the DbEntityValidationException then it means that model is not in sync with the database. Try recreating the model from the database because it's still the easiest way to determine the problematic field.
–
CiprianOct 17 '13 at 9:16

Same here. On my SaveChanges in EF6.01 where one field is too long, I get a SqlException as the inner exception inside a UpdateException inside a DbUpdateException. My model is in sync.
–
DaveJul 11 '14 at 3:09

Not sure about truncation specifically, but here is a tip for when you get an exception that tells you to examine EntityValidationErrors. Usuaully when debugging it won't let you see that property (unless you already had an explicit catch). However, you can open up quick watch and type $exception. Now you should be able to drill in and find that property. You can also just type the following: