Watch out for this feature, not a bug thingy:
In a Data Flow Task, my OLE DB Destination started to fail intermittently for no appearent reason. The error message was "Cursor Operation Conflict". Some head scratching later I discovered that the SQL Server 2005 database instance had had it's "no count" connection option changed to ON (the default after installation is OFF.)
It seems that ADO expects getting back row counts, and gets confused when they're missing. Here's the culprit:
Here’s some background information.
In short, make sure that the database instances that SSIS uses has the "no count" connection setting turned off (i.e. NO check mark for the "no count" property in the above dialog.)
Happy hacking!