Yep, that was it. It was hard, but we finally traced the issue to a null value in a user defined field.
↧