I just had the same problem.

It turned out that the stored procedure had two columns with the same name, but different cases:

CreatedOn and createdon.

Normally the source task flags this as a duplicate column, but it didn't in this case.

Once I removed the duplicated column from the stored procedure, the error went away.