Since we have enabled Merge replication on our tables, some of our SSIS packages have broken.
The issue is always the same, update statements sent to certain tables through an OLE DB Command are broken.
The error message is
"The metadata could not be determined because statement ‘exec @retcode = sys.xp_mapdown_bitmap @mapdownbm, @bm output’ in procedure ‘sp_mapdown_bitmap’ invokes an extended stored procedure.
Unable to retrieve destination column descriptions from the parameters of the SQL Command."
Some Googeling brought us to this link, though it is for SQL 2005 and we are using SQL 2012:
"http://social.technet.microsoft.com/Forums/sqlserver/en-US/67519e6a-d4cf-49ba-93dd-b0eb5229fb92/replication-trigger-problem-sql-2005-assistance-please?forum=sqlreplication"
And indeed, since then we have found out that the issue only occurs on tables whose Merge Replication trigger contain a call to sp_mapdown_bitmap. Different from the article above, we only have the issue in SSIS. The same update statement executed from SSMS works without a problem. We even tried makeing a SP that performs the update, and then calling that SP from SSIS, but no luck. The SP runs perfectly from SSMS but won't validate on SSIS.
Offcourse, recreating the tables in question would solve the problem for now, but we need a more permanent solution. Columns will be added and removed in the futur, and recreating a table each time that happends isn't realistic.