Steve,

That's exactly what was happening. There is an occasional zero in the data ( at row 36, in this case ) but SQL server kept on showing the error at row...