ODBC driver is not compatible with .NET 2.0 SP2 and .NET 3.5 SP1 [ODBC71] #70
Comments
|
Commented by: @samofatov Fixed in driver HEAD (future 2.1) |
Modified by: @samofatovstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] assignee: Nickolay Samofatov [ skidder ] |
Modified by: @alexpotapchenkostatus: Resolved [ 5 ] => Closed [ 6 ] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Submitted by: Roman Kisluhin (roman kisluhin)
Assigned to: @samofatov
MSSQL SSIS package reports about error (SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR) while fetching data from Firebird. This error occurs only when .NET 2.0 Service Pack 2 installed.
There is some description about the error by Microsoft: http://blogs.msdn.com/sqlblog/archive/2009/04/09/after-installation-of-net-framework-3-5-sp1-or-net-framework-2-0-sp2-ssis-packages-using-odbc-3rd-party-drivers-may-fail.aspx.
This happens on fields of BLOB and other data types with variable length (e.g. varchar) with zero length (empty fields).
SSIS calls sqlGetData function twice: first time to determine the buffer size, second time to fetch the data. ODBC driver returns 0 in first case, but for second returns SQL_NO_DATA error (because of length of the data is 0). As we can realize, the ODBC driver should return SQL_SUCCESS and fill the buffer with empty value in such case.
Commits: 773757d d1c06ed
The text was updated successfully, but these errors were encountered: