I have a package that I developed in SSIS 2005 and recently ported to 2008. Everything runs great except an OLE DB Command component that calls a stored procedure that uses output parameters.
When I try to run this, I get this error:
Error: 0xC0202009 at Data Flow Task, OLE DB Command : SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80004005 Description: "Syntax error, permission violation, or other nonspecific error".
Error: 0xC004701A at Data Flow Task, SSIS.Pipeline: component "OLE DB Command" (100) failed the pre-execute phase and returned error code 0xC0202009.
When I do the same thing in SSIS2005, it works fine.
So I setup a new package with 1 data flow. In that data flow, I added a source component, an OLE DB Command, and a destination. I then tested this with a stored procedure that took no parameters. It worked fine.
I then tested it with a stored procedure with 1 parameter defined as OUTPUT. This generated the error.
Is there an issue with output parameters in an OLE DB Command in SSIS 2008?
View Complete Post